CVE-2023-23488 is an unauthenticated SQL injection vulnerability affecting the Paid Memberships Pro WordPress plugin before version 2.9.8. The flaw is present in handling of the code parameter in the plugin's /pmpro/v1/order REST API route. Insufficient sanitization or parameterization of attacker-controlled input allows crafted requests to alter backend SQL queries. Because the vulnerable endpoint is reachable without authentication, remote attackers can attempt exploitation directly against exposed WordPress installations running affected plugin versions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit auxiliary scanner module targeting a SQL injection vulnerability (CVE-2023-23488) in the Paid Memberships Pro WordPress plugin (versions prior to 2.9.8). The exploit is unauthenticated and leverages a time-based blind SQL injection via the 'code' parameter in the /pmpro/v1/order REST API endpoint. The module is capable of extracting usernames and password hashes from the wp_users table of the affected WordPress installation. The extracted hashes can be cracked offline to obtain valid credentials. The module is operational, providing real exploitation capability, and is implemented in Ruby as part of the Metasploit framework. The repository is structured as a single Ruby file under the Metasploit modules directory.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.