# CVE-2023-23488: SQL injection in Paid Memberships Pro WordPress Plugin

> Unauthenticated attackers can execute SQL commands via the order REST route, potentially reading or modifying database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-pppw-hpjp-v2p9

## What is CVE-2023-23488?

CVE-2023-23488 is a critical SQL injection vulnerability in Paid Memberships Pro WordPress Plugin, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Paid Memberships Pro WordPress Plugin, version < 2.9.8, is affected by an unauthenticated SQL injection vulnerability in the 'code' parameter of the '/pmpro/v1/order' REST route.

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

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

It affects 1 product.


Products: Strangerstudios Paid Memberships Pro.

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

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

## Is CVE-2023-23488 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23488 exists.

Public exploit code:

- Paid Memberships Pro  v2.9.8 (WordPress Plugin) - Unauthenticated SQL Injection (github_poc): https://github.com/cybfar/CVE-2023-23488-pmpro-2.8
- Wordpress Paid Membership Pro code Unauthenticated SQLi (metasploit)
- Unauthenticated SQL Injection - Paid Memberships Pro < 2.9.8 (WordPress Plugin) (github_poc): https://github.com/long-rookie/CVE-2023-23488-PoC
- Paid Memberships Pro  v2.9.8 (WordPress Plugin) - Unauthenticated SQL Injection (exploitdb)
- WordPress Paid Memberships Pro <2.9.8 - Blind SQL Injection (nuclei): http/cves/2023/CVE-2023-23488.yaml

## Other vulnerabilities in Paid Memberships Pro WordPress Plugin

- [CVE-2021-25114](https://insights.sbomify.com/CVE-2021-25114/): Paid Memberships Pro < 2.6.7 - Unauthenticated Blind SQL Injection (critical 9.8)
- [CVE-2023-0631](https://insights.sbomify.com/CVE-2023-0631/): Paid Memberships Pro < 2.9.12 - Subscriber+ SQL Injection (high 8.8)
- [CVE-2021-20678](https://insights.sbomify.com/CVE-2021-20678/): SQL injection in Paid Memberships Pro (high 8.8)
- [CVE-2024-37486](https://insights.sbomify.com/CVE-2024-37486/): WordPress Paid Memberships Pro plugin <= 3.0.5 - Authenticated SQL Injection vulnerability (high 7.6)
- [CVE-2024-37277](https://insights.sbomify.com/CVE-2024-37277/): WordPress Paid Memberships Pro plugin <= 3.0.4 - Insecure Direct Object References (IDOR) vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23488 is a critical SQL injection vulnerability in Paid Memberships Pro WordPress Plugin, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-23488 exists.

Affected product: Paid Memberships Pro WordPress Plugin. 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-23488/ (Markdown: https://insights.sbomify.com/CVE-2023-23488/index.md)
```

## Sources

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

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