LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36690: WordPress WPLMS Theme < 4.900 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in VibeThemes WPLMS theme <= 4.900 versions.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A WordPress site using the VibeThemes WPLMS theme may let an attacker trick a signed-in user into making unwanted changes. The CVE rates the impact as high for integrity and availability, but the public bundle does not describe the exact vulnerable action or confirmed fixed release.

Executive priority

Treat this as a high-priority WordPress theme exposure where WPLMS is deployed. Prioritize internet-facing learning-management sites and any site with many privileged editors, because successful CSRF can affect site integrity or availability.

Technical view

CVE-2023-36690 is a CSRF flaw in VibeThemes WPLMS, described as affecting versions up to 4.900. CVSS 3.1 is 8.1 with network attack vector, low complexity, no attacker privileges, required user interaction, no confidentiality impact, and high integrity and availability impact.

Likely exposure

Exposure is most likely on WordPress sites with the WPLMS theme installed, especially versions at or below the affected range. The source data has incomplete CPE/package version detail, so confirm exposure from the installed theme metadata and vendor advisory.

Exploitation context

The bundle does not show CISA KEV listing or cite active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF, where a victim’s browser may be induced to submit an unintended request.

Researcher notes

Public evidence is sparse. The CVE describes WPLMS versions up to 4.900, while the Patchstack URL text references 4.600, so preserve that discrepancy in triage notes. No endpoint, proof of concept, exploit activity, or fixed version is provided in the bundle.

Mitigation direction

  • Check VibeThemes and Patchstack guidance for the fixed WPLMS release.
  • Update WPLMS only according to confirmed vendor guidance.
  • Disable or remove WPLMS on sites that do not require it.
  • Limit privileged WordPress sessions until remediation is confirmed.
  • Monitor administrative changes on affected WordPress sites.

Validation and detection

  • Inventory WordPress sites for the WPLMS theme.
  • Record installed WPLMS versions and compare with the advisory range.
  • Confirm whether WPLMS is active or merely installed.
  • Review vendor or Patchstack notes for fixed-version confirmation.
  • Check logs for unexpected administrative changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-36690 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H2.85.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2023-36690Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VibeThemesWPLMSwplms, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.