CVE-2026-62059 is a blind SQL injection vulnerability in the Ultimate Member WordPress plugin. Improper neutralization of special elements in SQL commands allows an attacker to perform blind SQL injection. Versions through 2.13.1 are affected.
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.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This nine-file repository is an authorized validation lab and functional Python proof of concept for CVE-2026-62059 in the WordPress Ultimate Member plugin. The primary exploit, poc/poc_cve_2026_62059.py, logs in as a WordPress administrator, retrieves edit nonces for a member-directory post, and saves a malicious value in _um_search_include_fields. In affected versions, the unregistered directory metadata key is stored without sanitization and later concatenated into the SQL meta_key IN(...) clause during a member-directory AJAX search. The PoC uses paired 1=1 and 1=2 payloads and a seeded usermeta marker to verify exploitation through a total_users count differential. It is operational but limited to a non-destructive boolean oracle. The Bash lab driver provisions fresh Dockerized WordPress/MySQL environments for Ultimate Member 2.13.1 and patched 2.14.0, verifies both the vulnerable and negative-control paths, and binds the web service only to localhost. A separate Nuclei YAML file performs only a one-request version screen of the publicly accessible plugin readme.txt; it cannot perform the administrator save-and-trigger chain. Repository code includes Python, Bash, and YAML, with Docker Compose configuration and GitHub Actions validation.
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.