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

CVE-2026-8880

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 RomanCart Ecommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'blclass' attribute (and other attributes) of the romancart_button shortcode in versions up to, and including, 2.0.8. This is due to insufficient input sanitization and output escaping on user supplied attributes within the romancart_button_shortcode() function. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 RomanCart Ecommerce WordPress plugin up to version 2.0.8 contains a Stored XSS vulnerability in the romancart_button_shortcode() function. The 'blclass' attribute and other shortcode attributes are not properly sanitized before output, allowing authenticated users with contributor-level access to inject arbitrary JavaScript that executes when other users view affected pages.

MitigationUpdate the RomanCart Ecommerce plugin to version 2.0.9 or later, which should include proper input sanitization using functions like esc_attr() and output escaping. If no update is available, implement sanitization on all shortcode attributes before output rendering.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify if RomanCart Ecommerce plugin is installed
    Navigate to WordPress admin > Plugins and look for 'RomanCart Ecommerce' in the installed plugins list
    Affected if The plugin is installed and active
  2. Determine the installed plugin version
    Click on the RomanCart Ecommerce plugin in the Plugins list to view its details, or check the plugin header in /wp-content/plugins/romancart-ecommerce/romancart.php for the Version field
    Affected if The version cannot be determined or falls within a vulnerable range (verify against any official security advisories)
  3. Search for usage of the romancart_button shortcode
    Search your WordPress database (wp_posts table) for content containing '[romancart_button' using a database query: SELECT * FROM wp_posts WHERE post_content LIKE '%[romancart_button%' AND post_status='publish';
    Affected if The shortcode is found in published content
  4. Inspect shortcode attributes for unsanitized input
    Examine the romancart_button shortcode instances in the database, specifically look for the blclass attribute: SELECT post_content FROM wp_posts WHERE post_content LIKE '%[romancart_button%';
    Affected if The blclass attribute contains unescaped characters like quotes, angle brackets, or suspicious patterns (e.g., javascript:, onload=)
  5. Check for stored XSS payloads in the database
    Review the raw database entries for the shortcode for any JavaScript-related patterns in attributes: SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%onclick=%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%script%';
    Affected if Malicious JavaScript payloads are present in shortcode attributes

You are affected if the RomanCart Ecommerce plugin is installed, the romancart_button shortcode is in use, and the blclass attribute contains unsanitized user-supplied data that could execute as JavaScript.

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 RomanCart Ecommerce plugin to version 2.0.9 or later, which should include proper input sanitization using functions like esc_attr() and output escaping. If no update is available, implement sanitization on all shortcode attributes before output rendering.

Recommended fix Moderate confidence

A version newer than 2.0.8 from the WordPress plugin repository (check plugins.trac.wordpress.org for availability)

  1. Check the WordPress plugin repository for RomanCart Ecommerce at plugins.trac.wordpress.org to confirm if a version newer than 2.0.8 is available with a security fix
  2. If a newer version exists, update the plugin through the WordPress admin dashboard or via wp-cli: wp plugin update romancart-ecommerce
  3. If no fixed version is available on the repository, consider temporarily removing the romancart_button shortcode from pages or disabling the plugin until a patch is released
  4. If the plugin must remain in use, implement content filtering to restrict contributor-level users from editing pages containing the shortcode
  5. Audit existing pages for any injected malicious scripts in the blclass attribute or other shortcode attributes

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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