Skip to main content
Menu
CVEs

Tribulant Newsletters unauthenticated SQL injection in WordPress plugin

CVE-2026-129043Published , updated

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 4.18.3
Who is exposed
Not reported

Summary

The Newsletters plugin (newsletters-lite) from Tribulant Software contains an SQL injection flaw that lets an attacker read sensitive data from the site's database. It can be reached remotely, without logging in.

Written by a model

Original description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Tribulant Software Newsletters newsletters-lite allows SQL Injection.This issue affects Newsletters: from n/a through 4.18.2.

Who should check

Teams running the Tribulant Software Newsletters WordPress plugin (newsletters-lite) at version 4.18.2 or earlier

“WordPress Newsletters Plugin <= 4.18.2 is vulnerable to a high priority SQL Injection”

patchstack.com

What to do

Upgrade to a fixed version: 4.18.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129043 (WordPress Newsletters plugin <= 4.18.2 - SQL Injection vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129043 (entry last updated 2026-11-20):
Affected:
- Tribulant Software Newsletters: fixed in 4.18.3
Fixed versions: 4.18.3.
Conditions (all must be true for the bug to be hit):
- WordPress Newsletters plugin version 4.18.2 or earlier (source: https://patchstack.com/database/wordpress/plugin/newsletters-lite/vulnerability/wordpress-newsletters-plugin-4-18-2-sql-injection-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129043 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129043 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/newsletters-lite/vulnerability/wordpress-newsletters-plugin-4-18-2-sql-injection-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-129043
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129043
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129043"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 3

Questions about CVE-2026-129043

Is CVE-2026-129043 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The plugin's SQL Injection flaw lets an attacker read, modify, or delete the entire site database, including user accounts and private data.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-129043?

newsletters-lite: through 4.18.2 (fixed in 4.18.3).

Source: cve.now feed data

Am I affected, and how do I check?

WordPress Newsletters plugin by Tribulant Software, version 4.18.2 and earlier, is affected. You can check the installed version on the Plugins screen of your WordPress admin.

Source: patchstack.com, cve.org

How do I fix CVE-2026-129043?

Update the Newsletters plugin to version 4.18.3 or later, the fixed version named in the advisory.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.