dbcve.org
Woocommerce SubscriptionsWordPress extension · Automattic

CVE-2023-35914

HIGH · 7.5 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to 5.1.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Authorization Bypass Through User-Controlled Key vulnerability in WooCommerce Woo Subscriptions.This issue affects Woo Subscriptions: from n/a through 5.1.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 confidence

An authorization bypass vulnerability exists in WooCommerce Woo Subscriptions where user-controlled input is used as a key to access sensitive subscription data or functionality without proper authorization validation. This IDOR-like flaw allows attackers to potentially access or manipulate subscription resources belonging to other users.

MitigationUpgrade Woo Subscriptions to the latest version (5.1.3 or later) which contains the patched authorization logic. If immediate patching is not possible, review access controls on subscription-related endpoints and implement additional authorization checks.

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
Woocommerce SubscriptionsWordPress extension
Affected:< 5.1.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed WooCommerce Subscriptions version
    Navigate to Plugins > Installed Plugins in WordPress admin, locate 'WooCommerce Subscriptions', and note the version number. Alternatively, check the main plugin file header or composer.json for the version.
    Affected if The installed version is lower than 5.1.3 (e.g., 5.1.2, 5.0.x, 4.x, etc.)
  2. Identify subscription-related endpoints accepting user input
    Review your site's subscription endpoints (typically /subscriptions/, /subscription/, or API endpoints like /wp-json/wc/v3/subscriptions) and identify which accept ID parameters in the URL or request body.
    Affected if Endpoints that accept subscription IDs or keys as URL parameters without requiring explicit user authentication to that specific subscription
  3. Test for missing authorization on subscription data access
    Using two different user accounts, attempt to access or modify a subscription belonging to the first user by providing the subscription ID in a request as the second user. Check if the request succeeds without proper ownership validation.
    Affected if A user can access or manipulate another user's subscription data by manipulating the subscription ID parameter
  4. Review subscription API key usage
    If your integration uses API keys for subscription access, verify that the API key or token is properly validated against the requested subscription's owner before returning data.
    Affected if API keys are accepted as valid without checking if the key belongs to the user requesting the specific subscription data

You are affected if WooCommerce Subscriptions is installed at a version below 5.1.3 and subscription data can be accessed by providing a subscription ID without proper ownership validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.1.3 or later
Fixed in 5.1.3
Interim mitigation

Upgrade Woo Subscriptions to the latest version (5.1.3 or later) which contains the patched authorization logic. If immediate patching is not possible, review access controls on subscription-related endpoints and implement additional authorization checks.

Recommended fix High confidence

WooCommerce Subscriptions version 5.1.3

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find WooCommerce Subscriptions in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 5.1.3
  5. 5. Alternatively, update via WP-CLI: wp plugin update woocommerce-subscriptions
  6. 6. After updating, verify the version number matches 5.1.3
  7. 7. Test that subscription-related functionality (user subscription management, renewal processing) works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Woocommerce Subscriptions Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35914 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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