WoopaymentsWordPress extension · Automattic
CVE-2023-35916
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo.This issue affects WooPayments – Fully Integrated Solution Built and Supported by Woo: from n/a through 5.9.0.
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 confidenceThis is an authorization bypass vulnerability in the WooPayments plugin where user-controlled keys allow attackers to bypass proper authorization checks. The vulnerability affects all versions from unknown/n/a through 5.9.0, allowing unauthorized access to payment-related functions or data.
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
WoopaymentsWordPress extension
< 5.9.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 WooPayments plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WooPayments' or check the file /wp-content/plugins/woopayments/ existsAffected if WooPayments plugin is present on the WordPress site
-
Check installed WooPayments versionIn WordPress admin, go to Plugins > Installed Plugins, find WooPayments, and note the version number. Alternatively, check the version in /wp-content/plugins/woopayments/readme.txt or the plugin header in /wp-content/plugins/woopayments/woopayments.phpAffected if The version listed is below 5.9.1 (for example, 5.9.0, 5.8.x, etc.)
-
Confirm WooPayments is activeIn WordPress admin > Plugins, verify that WooPayments shows as 'Active' rather than 'Inactive'Affected if WooPayments is active and version is below 5.9.1
If WooPayments is installed, active, and the version is below 5.9.1, the site is affected by this authorization bypass vulnerability.
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 · scoped5.9.1
Upgrade WooPayments to the latest patched version once released. Until then, restrict administrative access to trusted personnel and monitor for suspicious payment activity.
5.9.1 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WooPayments in the plugin list
- Check the current version number to confirm it is below 5.9.1
- If an update is available, click 'Update Now' to upgrade to version 5.9.1 or later
- Alternatively, navigate to Dashboard > Updates to check and apply available updates
- After updating, verify the new version number confirms the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woopayments
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35916 — 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-35916 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