# CVE-2024-43315: WordPress Stripe Payments For WooCommerce plugin <= 1.9.1 - Insecure Direct Object References (IDOR) vulnerability

> Attackers can bypass authorization checks to access or modify data via user-controlled keys in the Stripe Payments for WooCommerce plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-4q5x-jwj9-qgpw

## What is CVE-2024-43315?

CVE-2024-43315 is a high-severity missing authorization vulnerability in Stripe Payments For WooCommerce by Checkout, published on 18 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-43315?


## How do I fix CVE-2024-43315?

No fix has been published for CVE-2024-43315 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-43315 being exploited?

There is no known exploitation of CVE-2024-43315 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-43315 and fix it if it is affected.

What it is: CVE-2024-43315 is a high-severity missing authorization vulnerability in Stripe Payments For WooCommerce by Checkout, published on 18 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-43315 in the wild and no public exploit code.

Affected product: Stripe Payments For WooCommerce by Checkout. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-43315/ (Markdown: https://insights.sbomify.com/CVE-2024-43315/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-43315
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-43315
- OSV: https://osv.dev/vulnerability/CVE-2024-43315

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-43315/
Summaries are generated and may contain mistakes; the official description above is the record.