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

CVE-2026-6864

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The CBX 5 Star Rating & Review plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'page' parameter in all versions up to, and including, 1.0.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrator into performing an action such as clicking on a link.

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 · high confidence

The CBX 5 Star Rating & Review WordPress plugin versions up to 1.0.7 contains a reflected Cross-Site Scripting vulnerability in the 'page' parameter. Attackers can inject arbitrary JavaScript through this parameter due to insufficient input sanitization and output escaping. Successful exploitation requires tricking an administrator into clicking a malicious link, causing the injected script to execute in the admin's browser session.

MitigationUpdate the CBX 5 Star Rating & Review plugin to a version beyond 1.0.7 which should include proper sanitization of the 'page' parameter and output escaping.

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
None

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

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 the CBX 5 Star Rating plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'CBX 5 Star Rating & Review' or check the /wp-content/plugins/ directory for a folder named 'cbx5star' or similar.
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In the WordPress Plugins admin page, locate the plugin and read the version number displayed below the plugin name, or open the plugin's main PHP file (usually in wp-content/plugins/cbx5star/) and check the plugin header for 'Version:' tag.
    Affected if The version displayed is 1.0.7 or lower
  3. Compare against affected version range
    The affected versions are any version up to and including 1.0.7. If your installed version is 1.0.7 or any earlier version (e.g., 1.0.6, 1.0.5, etc.), the vulnerability exists.
    Affected if Installed version is 1.0.7 or below (e.g., 1.0.0, 1.0.1, 1.0.6)
  4. Check for exposure to the vulnerable 'page' parameter
    Review the plugin's code files for usage of the 'page' GET/REQUEST parameter without sanitization via sanitize_text_field() or similar WordPress sanitization functions, and without output escaping via esc_html() or esc_attr().
    Affected if The 'page' parameter is used in output without sanitization and escaping functions

You are affected if the CBX 5 Star Rating & Review plugin is installed at version 1.0.7 or any earlier version and the vulnerable 'page' parameter handling is present in the code.

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 the CBX 5 Star Rating & Review plugin to a version beyond 1.0.7 which should include proper sanitization of the 'page' parameter and output escaping.

Recommended fix Moderate confidence

CBX 5 Star Rating & Review version 1.0.8 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find CBX 5 Star Rating & Review plugin
  4. Click Update Now or check for updates and update the plugin
  5. After update, verify the version is 1.0.8 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6864 — 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-6864 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