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

CVE-2026-6725

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-28
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 WPC Smart Messages for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'text' attribute of the `wpcsm_text_rotator` shortcode in all versions up to, and including, 4.2.8. This is due to insufficient input sanitization and output escaping on user supplied attributes. 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 WPC Smart Messages for WooCommerce plugin fails to sanitize and escape the 'text' attribute in the wpcsm_text_rotator shortcode, allowing authenticated contributors+ to inject persistent JavaScript that executes for all users visiting affected pages.

MitigationUpdate the plugin beyond version 4.2.8, or add sanitize_text_field() during input handling and esc_html()/esc_attr() during output rendering for the text attribute.

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. Confirm plugin installation
    Navigate to WP Admin > Plugins and locate 'WPC Smart Messages for WooCommerce' in the list of installed plugins
    Affected if The plugin is not installed or has been removed entirely
  2. Check installed version
    In WP Admin > Plugins, find the plugin and view the version number displayed beneath the plugin name
    Affected if The installed version is 4.2.8 or lower
  3. Identify usage of vulnerable shortcode
    Search the WordPress database or wp_posts table for occurrences of '[wpcsm_text_rotator' using a database query or a plugin that searches post content
    Affected if Any posts, pages, or widget content contain the wpcsm_text_rotator shortcode
  4. Inspect shortcode attributes
    Examine the 'text' attribute value in any found wpcsm_text_rotator shortcode usage; look for unescaped HTML or JavaScript in the attribute value
    Affected if The 'text' attribute contains raw, unescaped characters that could represent malicious script tags or event handlers

A user is affected if the WPC Smart Messages plugin is installed at version 4.2.8 or below AND the wpcsm_text_rotator shortcode with a 'text' attribute is present in any published content.

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 plugin beyond version 4.2.8, or add sanitize_text_field() during input handling and esc_html()/esc_attr() during output rendering for the text attribute.

Recommended fix Moderate confidence

4.2.9 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WPC Smart Messages for WooCommerce' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/wpc-smart-messages and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the version number reflects 4.2.9 or later

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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