WoopaymentsWordPress extension · Automattic
CVE-2023-51503
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 6.9.2.
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 confidenceAn authorization bypass vulnerability in WooPayments allows attackers to potentially manipulate user-controlled keys (such as object IDs or parameters) to access unauthorized data or functionality without proper permission validation. This could enable unauthorized access to sensitive payment information or administrative functions within the WooCommerce payment ecosystem.
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
< 6.7.0CVSS 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 the WordPress admin dashboard, navigate to Plugins > Installed Plugins and locate WooPayments in the list, or check for the presence of the /wp-content/plugins/woopayments/ directory on the serverAffected if WooPayments plugin is not found in the WordPress installation
-
Locate the installed version numberIn WordPress admin, go to Plugins > Installed Plugins > WooPayments and read the version number from the plugin details, or open the main plugin file (typically woopayments.php) and check the 'Version' header in the plugin comment blockAffected if The version number cannot be determined from the plugin files
-
Compare version against affected rangeExamine the installed version number and determine if it is less than 6.7.0 (for example, 6.6.0, 6.5.2, or any 6.x.x version below 6.7.0)Affected if Installed version is any version prior to 6.7.0 (versions like 6.6.9, 6.6.0, 6.5.x, etc.)
If WooPayments is installed and the version number is below 6.7.0, the environment 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 · scoped6.7.0
Upgrade WooPayments to version 6.9.3 or later to receive the official patch that implements proper authorization validation for user-controlled key parameters.
WooPayments 6.7.0 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find WooPayments in the plugin list
- If an update is available, click 'Update Now' to update to the latest version
- Alternatively, manually download the latest WooPayments version from the WordPress plugin repository or WooCommerce marketplace
- After updating, verify the version number matches or exceeds 6.7.0
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-51503 — 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-51503 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