LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36692: WordPress WP-Cirrus Plugin <= 0.6.11 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Christian Kramer & Hendrik Thole WP-Cirrus plugin <= 0.6.11 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-36692 is a stored cross-site scripting issue in the WordPress WP-Cirrus plugin through version 0.6.11. It requires an authenticated admin-level user and victim interaction, so broad internet-scale abuse is less likely, but a compromised or malicious admin could plant script content affecting site users or administrators.

Executive priority

Treat as a moderate WordPress hygiene issue. Prioritize sites where admin accounts are broadly shared, externally managed, or weakly protected; otherwise handle through normal plugin patch and decommissioning workflows.

Technical view

The CVE describes CWE-79 stored XSS in Christian Kramer and Hendrik Thole WP-Cirrus <= 0.6.11. CVSS 3.1 is 5.9 with network access, low complexity, high privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites running the WP-Cirrus plugin at version 0.6.11 or earlier. Sites without this plugin are not affected based on the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires admin-level authentication and user interaction, which reduces likelihood but matters if admin accounts are shared, weakly protected, or already compromised.

Researcher notes

Evidence is sparse in the provided bundle. The CVE identifies stored XSS and privilege requirements but does not include affected code paths, proof-of-concept details, exploit telemetry, or a fixed version. Avoid assuming more than WP-Cirrus <= 0.6.11 is affected.

Mitigation direction

  • Inventory WordPress sites for the WP-Cirrus plugin and installed version.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release or official remediation.
  • Restrict admin access to trusted users with MFA and least privilege.
  • Consider disabling WP-Cirrus where it is unnecessary or unsupported.
  • Review administrative changes around plugin-managed content or settings.

Validation and detection

  • Confirm whether wp-cirrus is installed on each WordPress site.
  • Record the exact WP-Cirrus version and compare against <= 0.6.11.
  • Check that admin accounts are current, expected, and protected by MFA.
  • Review recent admin activity for unexpected content or configuration changes.
  • Verify any vendor-recommended update or removal after applying it.
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-79: 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-36692 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
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

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

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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-36692Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Christian Kramer & Hendrik TholeWP-Cirruswp-cirrus, n/aunaffected
Weakness

CWE details

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