CVE-2026-0552
Stored XSS in Simple Shopping Cart WordPress Plugin Allows Script Injection
Publication date: 2026-04-04
Last updated on: 2026-04-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Simple Shopping Cart plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) via its 'wpsc_display_product' shortcode in all versions up to and including 5.2.4. This vulnerability arises because the plugin does not properly sanitize or escape user-supplied attributes. As a result, authenticated attackers with contributor-level access or higher can inject arbitrary web scripts into pages. These scripts execute whenever any user accesses the injected page.
How can this vulnerability impact me? :
This vulnerability allows attackers with contributor-level access or above to inject malicious scripts into pages viewed by other users. The impact includes potential theft of user credentials, session hijacking, defacement of website content, or execution of unauthorized actions on behalf of users. Since the vulnerability is a Stored Cross-Site Scripting issue, the malicious code persists on the site and affects all visitors to the compromised pages.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves Stored Cross-Site Scripting (XSS) via the 'wpsc_display_product' shortcode in the Simple Shopping Cart WordPress plugin up to version 5.2.4. Detection involves identifying if your WordPress installation uses this plugin version and if any pages contain injected scripts via this shortcode.
You can detect the vulnerability by checking the plugin version installed on your WordPress site and scanning for suspicious script injections in pages using the shortcode.
- Check the installed plugin version via WP-CLI: `wp plugin list | grep simple-paypal-shopping-cart`
- Search for the shortcode usage in your WordPress content database: `wp db query "SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%[wpsc_display_product]%'"`
- Scan pages containing the shortcode for suspicious script tags or unusual attributes that could indicate XSS payloads.
- Use web vulnerability scanners or manual inspection tools to detect stored XSS payloads in pages rendered by the plugin.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the Simple Shopping Cart plugin to version 5.2.5 or later, where the vulnerability has been addressed by adding proper input sanitization and output escaping.
If immediate updating is not possible, restrict contributor-level and higher user permissions to trusted users only, as the vulnerability requires authenticated users with contributor-level access or above to exploit.
Additionally, monitor and sanitize any user input that might be used in the 'wpsc_display_product' shortcode and consider disabling the shortcode temporarily if feasible.
Review and apply any security patches or updates related to Stripe post-checkout handling and output escaping as described in the plugin's changelog.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in the Simple Shopping Cart plugin allows authenticated attackers with contributor-level access to inject arbitrary web scripts via stored Cross-Site Scripting (XSS). This can lead to unauthorized access or manipulation of user data when users access the injected pages.
Such security weaknesses can impact compliance with standards and regulations like GDPR and HIPAA, which require protection of personal data and secure handling of user information to prevent unauthorized access or data breaches.
By enabling script injection, this vulnerability could potentially expose personal or sensitive data to attackers, thereby violating data protection requirements and increasing the risk of non-compliance with these regulations.