CVE-2023-47239
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Scott Paterson Easy PayPal Shopping Cart plugin <= 1.1.10 versions.
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 confidenceAuthenticated users with contributor-level permissions or higher can inject malicious JavaScript code through the Easy PayPal Shopping Cart plugin's input fields, which gets stored in the database and executes when other users view the affected pages, leading to stored cross-site scripting.
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<= 1.1.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Easy PayPal Shopping Cart plugin is installedCheck the WordPress plugins directory for the easy-paypal-shopping-cart folder, typically at wp-content/plugins/, or list installed plugins via WP-CLI: wp plugin list --name='easy-paypal-shopping-cart'Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress plugin list
-
Determine the installed plugin versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, find Easy PayPal Shopping Cart, and read the version number from the plugin description; alternatively, check the main plugin file header in wp-content/plugins/easy-paypal-shopping-cart/easy-paypal-shopping-cart.php for the 'Version' tagAffected if The displayed version number is 1.1.10 or lower
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify the Easy PayPal Shopping Cart shows as 'Active', or run: wp plugin status easy-paypal-shopping-cartAffected if The plugin is currently active and running
-
Identify if contributor-level or higher users existIn WordPress admin, go to Users > All Users and review the roles assigned; or query the wp_usermeta table for users with roles including 'contributor', 'author', 'editor', or 'administrator', or use WP-CLI: wp user list --role=contributorAffected if At least one user account has contributor-level permissions or higher
-
Check for suspicious stored data in plugin-related optionsQuery the wp_options table for entries related to the plugin (option_name containing 'eppsc' or 'easy_paypal'), and inspect the option_value fields for any HTML script tags or JavaScript event handlers; run SQL: SELECT * FROM wp_options WHERE option_name LIKE '%eppsc%' OR option_name LIKE '%easy_paypal%'Affected if Any option_value contains unescaped HTML script tags or javascript: protocols indicating stored XSS payloads
A user is affected if the Easy PayPal Shopping Cart plugin is installed with version 1.1.10 or lower and is currently active, with contributor-level or higher user accounts present in the WordPress environment.
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 dataUpdate the Easy PayPal Shopping Cart plugin to a version newer than 1.1.10 to obtain the patched version, or disable the plugin until a security update is available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47239 — 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-2023-47239 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