LiveActive security incident?Get immediate response
CVE Record

CVE-2023-23831: WordPress Rating Widget Plugin <= 3.1.9 is vulnerable to Cross Site Scripting (XSS)

Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Rating-Widget Rating-Widget: Star Review System plugin <= 3.1.9 versions.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites running Rating-Widget: Star Review System up to 3.1.9. A logged-in contributor or higher could store script content that runs when another user views affected content. The likely business impact is account/session abuse, content manipulation, or data exposure within WordPress. Sources do not show active exploitation.

Executive priority

Treat as a near-term WordPress hygiene issue, not an emergency, unless the plugin is present on high-value sites or contributor access is broad. Prioritize inventory, access review, and vendor-guided remediation.

Technical view

CVE-2023-23831 is an authenticated stored XSS issue (CWE-79) in package rating-widget, requiring network access, low complexity, contributor-level privileges, and user interaction. CVSS 3.1 is 6.5 with changed scope and low confidentiality, integrity, and availability impact. The bundle does not identify a vulnerable parameter, payload, or fixed release.

Likely exposure

Likely exposure is WordPress installations with the Rating-Widget: Star Review System plugin at version 3.1.9 or earlier, especially where contributor accounts are available to staff, contractors, authors, or compromised users.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not claim active exploitation. The attacker needs authenticated contributor-or-higher access and a victim interaction path. Stored XSS can become serious when privileged administrators view affected content.

Researcher notes

The public bundle establishes authenticated stored XSS, CVSS 6.5, CWE-79, affected plugin family, and <=3.1.9 scope. It does not provide sink details, proof-of-concept material, exact fixed version, or exploitation evidence, so validation should stay inventory- and vendor-guidance-driven.

Mitigation direction

  • Inventory WordPress sites for the rating-widget plugin and recorded version.
  • Check vendor or Patchstack guidance for a fixed version or recommended action.
  • Upgrade the plugin if a fixed release is available.
  • Disable or remove the plugin where business need is low.
  • Review contributor-level accounts and remove unnecessary access.

Validation and detection

  • Confirm whether rating-widget is installed on each WordPress site.
  • Verify installed versions are not 3.1.9 or earlier.
  • Review WordPress roles for contributor-or-higher accounts.
  • Check logs for unexpected contributor content changes.
  • Confirm remediation through plugin inventory after updates or removal.
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-23831 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
Rating-WidgetRating-Widget: Star Review Systemrating-widget, n/aunaffected
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.