Wordpress Ultra Simple Paypal Shopping CartWordPress extension · Ultra Prod
CVE-2019-5992
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 · uneditedCross-site request forgery (CSRF) vulnerability in WordPress Ultra Simple Paypal Shopping Cart v4.4 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.
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 confidenceCross-site request forgery (CSRF) vulnerability in WordPress Ultra Simple Paypal Shopping Cart plugin versions 4.4 and earlier allows remote attackers to hijack the authentication of administrators by tricking them into executing unintended administrative actions via forged requests.
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 Ultra Simple Paypal Shopping CartWordPress extension
<= 4.4CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedIn WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Ultra Simple Paypal Shopping Cart' or check the plugins directory for /wp-content/plugins/ultra-simple-paypal-shopping-cart/Affected if The plugin is installed and active in WordPress
-
Identify installed versionIn Plugins list, find the Ultra Simple Paypal Shopping Cart entry and note the version number displayed under the plugin name; alternatively, open the main plugin PHP file (e.g., ultra-simple-paypal-shopping-cart.php) and look for the 'Version' header in the file commentsAffected if Version displayed is 4.4 or earlier
-
Check if admin session is activeVerify that the WordPress site has administrator accounts and that admin-facing pages exist; CSRF requires an authenticated admin to inadvertently submit a forged requestAffected if Administrator accounts exist and the site allows admin login for management
-
Inspect admin forms for nonce tokensExamine the plugin's admin PHP files for presence of wp_nonce_field(), wp_nonce_url(), or check_admin_referer() function calls on forms that perform state-changing actions (e.g., settings saves, plugin configuration)Affected if No nonce/CSRF tokens are found in admin forms and the plugin version is 4.4 or earlier
A user is affected if the Ultra Simple Paypal Shopping Cart plugin version is 4.4 or earlier, is installed and active in WordPress, and the admin forms lack anti-CSRF token protection.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to WordPress Ultra Simple Paypal Shopping Cart version 4.5 or later which includes anti-CSRF token protection for all state-changing operations; alternatively, implement nonce/token validation on all admin-facing forms and actions.
Fix this in Wordpress Ultra Simple Paypal Shopping Cart
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5992 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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