Skip to main content
Mallory
High

Unauthenticated SQL Injection in WordPress Newsletters Plugin wpmlsubscriber_id Parameter

IdentifiersCVE-2026-3018CWE-89· Improper Neutralization of Special…

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation allows unauthenticated attackers to perform SQL injection against the WordPress site's backend database. Based on the provided information, the primary impact is extraction of sensitive information from the database through time-based blind techniques. Depending on database contents, this may expose subscriber data, WordPress user information, configuration data, and other application-resident secrets accessible to the vulnerable query context.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling the vulnerable Newsletters plugin or restricting access to the affected functionality where feasible. Deploying a WAF or virtual patch capable of detecting SQL injection payloads targeting the 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.

Update the Newsletters plugin to a version newer than 4.13 once a vendor-fixed release is available. The vulnerable code path should be corrected by strictly validating and type-enforcing the wpmlsubscriber_id parameter and by using properly parameterized queries/prepared statements for all database access involving user-supplied input.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.