dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2024-43315

HIGH · 7.5 CVSS v3.1 Published 2024-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Checkout Plugins Stripe Payments For WooCommerce by Checkout.This issue affects Stripe Payments For WooCommerce by Checkout: from n/a through 1.9.1.

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 in the Stripe Payments For WooCommerce plugin allows attackers to manipulate user-controlled keys (such as order IDs or payment parameters) to access or modify other users' payment data and transactions without proper authorization. This is a broken access control issue where the plugin fails to verify that the requesting user has permission to access the specific resource.

MitigationUpgrade to version 1.9.2 or later. In the meantime, restrict admin access to trusted personnel only and monitor for unusual access patterns to payment records.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Locate the installed Stripe Payments For WooCommerce version
    Access your WordPress admin dashboard, navigate to Plugins > Installed Plugins, find 'Stripe Payments For WooCommerce' and read the version number from the plugin description. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/stripe-payments-for-woocommerce/) for a version constant or header.
    Affected if The version shown is lower than 1.9.2 (e.g., 1.9.1, 1.9.0, 1.8.x, etc.) or if no version is displayed and you cannot confirm it is 1.9.2 or later.
  2. Confirm the plugin is active and processing payments
    In WordPress admin, verify the Stripe Payments For WooCommerce plugin shows as 'Active'. Additionally, confirm WooCommerce is active and that you have payment settings configured (WooCommerce > Settings > Payments).
    Affected if The plugin is active and WooCommerce payment processing is enabled, meaning the vulnerable code is running.
  3. Check if the payment flow handles user-controlled order IDs
    Review your payment processing workflow: when a payment is initiated, the plugin accepts order IDs or payment parameters directly from user requests without additional ownership verification. This can be tested by inspecting the plugin code for functions that process order IDs from $_POST or $_GET arrays without checking wp_get_current_user()->ID against the order owner.
    Affected if The plugin processes order IDs from frontend requests without verifying the current user owns that order, which is the core vulnerability behavior.
  4. Audit user access to payment records
    In WordPress admin, review WooCommerce > Orders to see if the plugin allows users to view or modify orders belonging to other users without proper authorization checks. Test by creating two test orders under different user accounts and attempting to access one while authenticated as the other.
    Affected if Users can access or modify payment records for orders they did not create, confirming the broken access control exists.

You are affected if the installed Stripe Payments For WooCommerce version is below 1.9.2 and the plugin is active with payment processing enabled, allowing unauthorized access to other users' payment data through manipulated order IDs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.9.2 or later. In the meantime, restrict admin access to trusted personnel only and monitor for unusual access patterns to payment records.

Have this fixed 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 help mitigating

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-2024-43315 — 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-2024-43315 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