CVE-2026-59550 is a critical SQL injection vulnerability affecting the WordPress AWP Classifieds plugin from Strategy11 in versions up to and including 4.4.7. The flaw is remotely exploitable without authentication, indicating that insufficient neutralization of attacker-controlled input in SQL queries allows arbitrary database commands to be injected and executed by the backend database. The issue affects publicly reachable vulnerable plugin functionality and can be triggered without user interaction. Successful exploitation can expose, alter, or disrupt application and site data stored in the WordPress database.
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.
This nine-file repository is an operational Python proof of concept for CVE-2026-59550 affecting the AWP Classifieds WordPress plugin through version 4.4.7. `exploit/exploit.py` drives an unauthenticated guest ad-submission workflow: it fetches the place-ad page for public nonces/captcha data, creates an anonymous auto-draft listing, obtains a per-listing save nonce, then sends `awpcp_save_listing_information` with SQL syntax embedded in a `regions` array key. The key reaches `AWPCP_BasicRegionsAPI::save()`, where unvalidated array keys become SQL identifiers in `$wpdb->insert()`/`update()`. The PoC converts this into a MySQL/MariaDB `SLEEP()` timing oracle, validates true/false conditions, and binary-search extracts query output. It is not framework-based and includes a configurable query option, but uses a basic hardcoded attack flow and payload construction. Supporting materials comprise a detailed technical writeup, a minimal `requests` dependency file, Docker Compose infrastructure for WordPress 6.8/MariaDB 11 vulnerable and patched instances, Bash provisioning/cleanup scripts, and the 4.4.8 patch. The patch addresses the issue by allowlisting database column names and accepted submitted-region fields before persistence.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.