Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-3018 – Unauthenticated SQL Injection – Newsletters WordPress Plugin ≤ 4.13

Be the first to know when new zero-days emerge:

Summary

CVE-2026-3018 is a high-severity, unauthenticated time-based SQL Injection vulnerability in the Newsletters plugin for WordPress (by Tribulant Software), affecting all versions up to and including 4.13. The flaw exists in the wpmlsubscriber_id parameter of the newsletters_management shortcode and allows any unauthenticated remote attacker to extract sensitive data from the WordPress database. A patched version (4.14) has been released and immediate upgrade is strongly recommended.

Technical details

  • Root cause: Insufficient escaping of the user-supplied wpmlsubscriber_id parameter combined with the absence of prepared statements ($wpdb->prepare()) in the SQL query built by the newsletters_management shortcode handler.
  • Trigger condition: The vulnerable code path is reachable without authentication or user interaction; any HTTP request to an affected site that triggers the shortcode endpoint is sufficient.
  • Attack vector: Remote, network-based. CVSS Attack Vector is NETWORK, with no privileges required and no user interaction (AC:L / PR:N / UI:N).
  • Exploitation technique: Time-based blind SQL injection — an attacker appends malicious SQL clauses to the existing query and infers database contents through observable response timing.
  • Impact: Full database read access (Confidentiality: HIGH). Exploitable data includes subscriber records, user credentials, session tokens, PII, and any other data stored in the WordPress database. Integrity and availability are not directly affected (I:N / A:N).

Affected software

  • Newsletters plugin for WordPress (slug: newsletters-lite, vendor: Tribulant Software / contrid)
    • All versions up to and including 4.13
  • Version 4.14 resolves this vulnerability by implementing parameterized queries via $wpdb->prepare() in the newsletters_management shortcode, as well as in several other previously vulnerable SQL execution paths.

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate – Apply the vendor patch: Upgrade the Newsletters plugin to version 4.14 or later. The fix is available directly from the WordPress Plugin Repository and through the standard WordPress admin dashboard (Plugins > Updates).
  • If immediate patching is not possible: Restrict public access to any WordPress pages or posts that embed the [newsletters_management] shortcode at the network or WAF level until the plugin can be updated.
  • General hardening: Review and rotate any credentials or sensitive data stored in the affected WordPress database as a precautionary measure in case exploitation occurred prior to patching.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge