CVE-2023-23488 in the critical feed json
The Paid Memberships Pro WordPress Plugin, version < 2.9.8, is affected by an unauthenticated SQL injection vulnerability in the 'code' par…
published 2023-01-20 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-27588
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 92.5%
- EPSS 92.5% chance of exploitation in 30 days, percentile 99.8%
- public exploits
- 2
- Metasploit, Exploit-DB, plus a Nuclei check
Summary
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.
Patch / fix
- strangerstudios paid_memberships_pro 2.9.8
Timeline
- First public exploit (Metasploit auxiliary/scanner/http/wp_paid_membership_pro_code_sqli)
- Published
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 19 mo ago
Exploit prediction
92.46% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/scanner/http/wp_paid_membership_pro_code_sqli Wordpress Paid Membership Pro code Unauthenticated SQLi metasploit auxiliary, normal rank, 2023-01-12
- EDB-51235 Paid Memberships Pro v2.9.8 (WordPress Plugin) - Unauthenticated SQL Injection webapps, 2023-04-03
- Nuclei template WordPress Paid Memberships Pro <2.9.8 - Blind SQL Injection nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- n/a Paid Memberships Pro WordPress Plugin
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
Sources
- CVE List CVE-2023-23488
- NVD CVE-2023-23488
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.