# CVE-2023-35915: WordPress WooCommerce Payments Plugin <= 5.9.0 is vulnerable to SQL Injection

> Attackers can execute arbitrary SQL commands via the WooPayments plugin, potentially reading or modifying database contents.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-m6qj-fx7x-v24r

## What is CVE-2023-35915?

CVE-2023-35915 is a high-severity SQL injection vulnerability in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo, published on 20 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-35915?

It affects 1 product.


Products: Automattic Woopayments.

## How do I fix CVE-2023-35915?

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

## Is CVE-2023-35915 being exploited?

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

## Other vulnerabilities in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo

- [CVE-2023-35916](https://insights.sbomify.com/CVE-2023-35916/): WordPress WooCommerce Payments Plugin <= 5.9.0 is vulnerable to Insecure Direct Object References (IDOR) (high 7.5)
- [CVE-2023-49828](https://insights.sbomify.com/CVE-2023-49828/): WordPress WooCommerce Payments Plugin <= 6.4.2 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2023-51503](https://insights.sbomify.com/CVE-2023-51503/): WordPress WooCommerce Payments Plugin <= 6.6.2 is vulnerable to Insecure Direct Object References (IDOR) (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35915 and fix it if it is affected.

What it is: CVE-2023-35915 is a high-severity SQL injection vulnerability in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo, published on 20 Dec 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35915 in the wild and no public exploit code.

Affected product: Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo. 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-2023-35915/ (Markdown: https://insights.sbomify.com/CVE-2023-35915/index.md)
```

## Sources

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

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