dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57359

HIGH · 7.1 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated Cross Site Scripting (XSS) in ReviewX <= 2.3.10 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unauthenticated Cross-Site Scripting (XSS) vulnerability in the ReviewX WordPress plugin version 2.3.10 and below allows remote attackers to inject malicious JavaScript through unsanitized user input, likely in review submission fields or display areas.

MitigationUpdate ReviewX to the latest patched version; until available, implement WAF rules to filter XSS payloads and disable review submissions if critical.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ReviewX plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a 'reviewx' folder
    Affected if ReviewX plugin is present in the WordPress installation
  2. Identify installed ReviewX version
    In WordPress admin, view the plugin details from the Plugins page to see the version number, or read the main plugin PHP file header for the 'Version' tag
    Affected if The installed version is 2.3.10 or lower
  3. Verify review submission feature is active
    Go to ReviewX plugin settings in WordPress admin and check if the review submission form is enabled for public users
    Affected if Review submission is enabled and accessible to unauthenticated users
  4. Confirm submission allows user-generated content
    Inspect the review submission form fields (name, email, rating, review text) in the frontend to see if they accept user input without authentication
    Affected if Unauthenticated users can submit reviews containing custom text content
  5. Check if output escaping is applied to review display
    View a published review on the frontend and inspect the page source to see if review content is rendered as raw HTML or properly escaped
    Affected if Review content appears to render without sanitization in page source

A user is affected if ReviewX plugin versions 2.3.10 or below are installed with review submission enabled for unauthenticated users, as the lack of input sanitization allows XSS injection in review fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update ReviewX to the latest patched version; until available, implement WAF rules to filter XSS payloads and disable review submissions if critical.

Recommended fix Moderate confidence

ReviewX 2.3.11 or later (latest available version)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate the ReviewX plugin
  5. 5. Check if the current version is 2.3.10 or lower (vulnerable)
  6. 6. If vulnerable, click 'Update Now' to upgrade to the latest version, or manually download the latest version from the WordPress plugin repository
  7. 7. After updating, verify the plugin is running version 2.3.11 or higher
  8. 8. Test the review submission functionality to ensure the plugin still works correctly
Caveat ReviewX is a WordPress plugin; upgrading should not cause breaking changes but always test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57359 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data