Unauthenticated SQL Injection in WordPress Newsletters Plugin wpmlsubscriber_id Parameter
CVE-2026-3018 is a time-based SQL injection vulnerability in the Newsletters plugin for WordPress affecting all versions up to and including 4.13. The flaw is caused by insufficient escaping of the user-controlled wpmlsubscriber_id parameter and inadequate use of prepared statements in an existing SQL query. As a result, an unauthenticated attacker can inject SQL syntax into the backend query flow and leverage time-based techniques to infer and extract sensitive information from the WordPress site database.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
wpmlsubscriber_id parameter may help reduce exploitability, but should not be treated as a substitute for remediation. Additional defensive measures include minimizing database privileges used by the application and monitoring for anomalous time-based SQLi patterns in web and database logs.Remediation
Patch, then assume compromise.
wpmlsubscriber_id parameter and by using properly parameterized queries/prepared statements for all database access involving user-supplied input.Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
7 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.
The version that knows your environment.
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.