dbcve.org
Wordpress Simple Paypal Shopping CartWordPress extension · Tipsandtricks Hq

CVE-2025-3890

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-01
Fix available
A fix is available. Upgrade to 5.1.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 WordPress Simple Shopping Cart plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'wp_cart_button' shortcode in all versions up to, and including, 5.1.3 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

Stored XSS vulnerability in WordPress Simple Shopping Cart plugin's wp_cart_button shortcode. Authenticated attackers with contributor-level access can inject arbitrary JavaScript through unsanitized shortcode attributes due to insufficient input sanitization and output escaping.

MitigationUpgrade to version 5.1.4 or later which contains proper input sanitization and output escaping for shortcode attributes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wordpress Simple Paypal Shopping CartWordPress extension
Affected:< 5.1.4

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify the installed plugin and version
    Check the WordPress plugin directory (wp-content/plugins/wordpress-simple-paypal-shopping-cart) for the main PHP file and look for the version comment/header, or use WP-CLI: wp plugin list --name='wordpress-simple-paypal-shopping-cart' --format=table
    Affected if The plugin is installed with a version number less than 5.1.4
  2. Verify the wp_cart_button shortcode is in use
    Search the WordPress database for posts/pages containing the [wp_cart_button] shortcode. This can be done via WP-CLI: wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[wp_cart_button%' AND post_status='publish';" or by searching in the WordPress admin under Posts/Pages
    Affected if The shortcode [wp_cart_button] is present in any published content
  3. Confirm contributor-level or higher users exist
    Check WordPress user roles: wp user list --role=contributor --format=count, or via Users menu in WordPress admin to see if any accounts with contributor, author, editor, or administrator roles exist
    Affected if At least one authenticated user with contributor-level access or higher exists on the site
  4. Check shortcode attribute usage
    Review posts/pages containing [wp_cart_button] and examine if custom attributes (such as item_name, price, or custom fields) are being passed to the shortcode in the content
    Affected if The shortcode is used with custom attributes that could be manipulated

The environment is affected if the Tipsandtricks Hq Wordpress Simple Paypal Shopping Cart plugin version is below 5.1.4, the wp_cart_button shortcode is in use on the site, and authenticated users with contributor-level access exist who could exploit the stored XSS vulnerability.

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
Upgrade available Upgrade to 5.1.4 or later
Fixed in 5.1.4
Interim mitigation

Upgrade to version 5.1.4 or later which contains proper input sanitization and output escaping for shortcode attributes.

Recommended fix High confidence

5.1.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WordPress Simple Shopping Cart' (or 'Simple Paypal Shopping Cart')
  4. If an update is available, click 'Update Now'
  5. Alternatively, manually upload version 5.1.4 of the plugin from the WordPress Plugin Repository
  6. After updating, verify the plugin version shows 5.1.4 or higher

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

Fix this in Wordpress Simple Paypal Shopping Cart 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 the upgrade done

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-2025-3890 — 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-2025-3890 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