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

CVE-2026-0552

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-04
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 Simple Shopping Cart plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wpsc_display_product' shortcode in all versions up to, and including, 5.2.4 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 Simple Shopping Cart WordPress plugin fails to properly sanitize and escape user input in the 'wpsc_display_product' shortcode attributes. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript that persists in pages and executes when users view the injected content.

MitigationUpgrade to version 5.2.5 or later which addresses the input sanitization and output escaping vulnerabilities. As an interim control, review user permissions for shortcode usage or consider disabling the plugin until the patch is applied.

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 the Simple Shopping Cart plugin is installed
    Navigate to WordPress admin > Plugins and verify 'Simple Shopping Cart' is installed and active
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In Plugins list, click on 'Simple Shopping Cart' details to view the version number. Compare it to the patched version 5.2.5
    Affected if Installed version is lower than 5.2.5 (e.g., 5.2.4, 5.2.3, etc.)
  3. Search for wpsc_display_product shortcode usage
    Use WordPress search or a database query to find posts/pages containing the string 'wpsc_display_product' in the wp_posts table content
    Affected if Any posts or pages contain the wpsc_display_product shortcode with custom attributes
  4. Audit contributor+ user accounts
    In WordPress admin > Users, review accounts with Contributor, Author, Editor, or Administrator roles who could create or edit content containing shortcodes
    Affected if There are multiple contributor+ user accounts, especially unrecognized or suspicious ones

You are affected if the plugin version is below 5.2.5 AND content contains the wpsc_display_product shortcode with user-supplied attributes from contributor+ accounts.

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

Upgrade to version 5.2.5 or later which addresses the input sanitization and output escaping vulnerabilities. As an interim control, review user permissions for shortcode usage or consider disabling the plugin until the patch is applied.

Recommended fix Moderate confidence

latest version of Simple Shopping Cart (verify version 5.2.5 or higher contains the fix)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Simple Shopping Cart' plugin
  4. Check if an update is available and install the latest version
  5. Verify the updated version is at least 5.2.5 or higher
  6. Test that the wpsc_display_product shortcode functions correctly after the update

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
  • Testing3.0 h
  • Review / QA1.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-0552 — 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-0552 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