Paypal PaymentsWordPress extension · Woocommerce
CVE-2023-35917
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 WooCommerce PayPal Payments plugin <= 2.0.4 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WooCommerce PayPal Payments plugin affecting versions 2.0.4 and below. The flaw allows attackers to trick authenticated administrators into unknowingly performing unintended actions such as modifying payment settings or processing fraudulent transactions.
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
Paypal PaymentsWordPress extension
<= 2.0.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.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > WooCommerce PayPal Payments and view the version number displayed. Alternatively, check the plugin header in the main plugin file (typically in wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php) for the 'Version' tag.Affected if The displayed version is 2.0.4 or any version number lower than 2.0.4
-
Verify plugin is activeConfirm the WooCommerce PayPal Payments plugin is currently activated in the WordPress plugins list.Affected if The plugin is active and the version is 2.0.4 or below
-
Confirm admin user presenceCheck if there are users with Administrator role in WordPress (Users > All Users > filter by Administrator).Affected if Administrator accounts exist on the site, as the CSRF attack targets authenticated admins
You are affected if the WooCommerce PayPal Payments plugin version is 2.0.4 or lower and the plugin is active on a WordPress site with administrator accounts.
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.
dbcve · scopedUpdate the WooCommerce PayPal Payments plugin to the latest version to apply the security patch. Additionally, enforce SameSite cookie attributes and validate anti-CSRF tokens on sensitive admin actions.
Version 2.0.5 or later (any stable release above 2.0.4)
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the 'PayPal Payments' plugin
- Check if the current version is 2.0.4 or lower
- If vulnerable, click 'Update Now' to install the latest version
- Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- After update, verify the plugin is running version 2.0.5 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Paypal Payments
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35917 — 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-35917 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