LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2433: YARPP – Yet Another Related Posts Plugin <= 5.30.3 - Authenticated (Contributor+) Stored Cross-Site Scripting

The YARPP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'className' parameter in versions up to, and including, 5.30.3 due to insufficient input sanitization and output escaping. This makes it possible for contributor-level attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-2433 affects the WordPress YARPP plugin through version 5.30.3. A logged-in user with Contributor-level access or higher could store malicious script content that runs when someone views the affected page. The main business risk is browser-side compromise of site users or administrators, not server takeover.

Executive priority

Prioritize remediation on public WordPress sites with multiple content authors or uncertain account hygiene. This is not described as actively exploited, but stored XSS can affect administrators and visitors once planted.

Technical view

The issue is stored cross-site scripting in YARPP via the className parameter, caused by insufficient input sanitization and output escaping. The CVSS 3.1 score is 6.4 with low attack complexity, required low privileges, changed scope, and limited confidentiality and integrity impact. Availability impact is not indicated.

Likely exposure

Exposure is limited to WordPress sites running YARPP versions up to and including 5.30.3, especially where Contributor or higher accounts can create or modify affected content.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated Contributor-level access or higher, then victim page viewing. Treat compromised or over-permissioned WordPress accounts as a practical risk amplifier.

Researcher notes

Focus validation on the className handling path and the 5.30.3 code referenced in WordPress Trac. The patch changeset is relevant evidence, but the source bundle does not name a specific fixed release.

Mitigation direction

  • Identify WordPress sites running YARPP versions up to 5.30.3.
  • Check vendor or WordPress plugin guidance and update away from affected versions.
  • Review Contributor and higher WordPress accounts for necessity and legitimacy.
  • Remove suspicious affected content only after preserving evidence if incident response is needed.

Validation and detection

  • Inventory installed YARPP versions across WordPress properties.
  • Confirm whether any site permits untrusted Contributor-level posting.
  • Review recent YARPP-related content changes for unexpected script-bearing markup.
  • Verify updated plugin code includes sanitization and escaping changes referenced by the patch changeset.
Prepared
Confidence
high
Sources
5

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-2433 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
6.4 (3.1)
Known Exploited
No
Published

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

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
4Source 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
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
jeffparkerYARPP – Yet Another Related Posts Plugin0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.