dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3018

HIGH · 7.5 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Newsletters plugin for WordPress is vulnerable to time-based SQL Injection via the ‘wpmlsubscriber_id’ parameter in all versions up to, and including, 4.13 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Newsletters WordPress plugin (versions up to 4.13) contains a time-based blind SQL Injection vulnerability in the 'wpmlsubscriber_id' parameter. The vulnerability stems from insufficient input escaping combined with the absence of prepared statements in the underlying SQL query, allowing unauthenticated attackers to inject arbitrary SQL commands to exfiltrate data from the database.

MitigationUpdate the Newsletters plugin to a version beyond 4.13 which patches the SQL injection vulnerability. As a temporary measure, consider deploying a WAF rule to block requests containing SQL injection patterns in the wpmlsubscriber_id parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Newsletters plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Newsletters' or check the file system at wp-content/plugins/ for a newsletters folder
    Affected if The Newsletters plugin is not installed on the WordPress site
  2. Identify the installed version
    In WordPress admin Plugins page, find the Newsletters plugin and read the version number displayed beneath the plugin name. Alternatively, check the 'Version:' line in the plugin's main PHP file header (e.g., newsletters/newsletters.php)
    Affected if The installed version is 4.13 or lower (the vulnerability exists in all versions up to 4.13)
  3. Locate code using wpmlsubscriber_id parameter
    Search plugin PHP files for occurrences of 'wpmlsubscriber_id' using grep or a code editor: grep -r 'wpmlsubscriber_id' wp-content/plugins/newsletters/
    Affected if The parameter is found in the codebase, indicating the vulnerable code path exists
  4. Check if prepare() is used for SQL queries
    Examine files containing wpmlsubscriber_id and verify whether $wpdb->prepare() is called for SQL statements using this parameter. Look for direct concatenation or interpolation of the parameter into SQL queries
    Affected if The SQL queries using wpmlsubscriber_id do NOT use $wpdb->prepare() or equivalent prepared statements, leaving the parameter unsanitized

The environment is affected if the Newsletters plugin is installed with version 4.13 or lower AND the wpmlsubscriber_id parameter handling lacks $wpdb->prepare() statements in the SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Newsletters plugin to a version beyond 4.13 which patches the SQL injection vulnerability. As a temporary measure, consider deploying a WAF rule to block requests containing SQL injection patterns in the wpmlsubscriber_id parameter.

Recommended fix Moderate confidence

Newsletters plugin version 4.14 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Newsletters' plugin
  4. Check the current version installed
  5. If the installed version is 4.13 or lower, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the version number reflects the new release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3018 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3018 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data