Tribulant Newsletters remote code execution via PHP object injection
- Exploited
- No known exploitation
- Fix
- Fixed in 4.18.3
- Who is exposed
- Not reported
Summary
The Newsletters plugin for WordPress, published by Tribulant Software, contains a PHP object injection flaw caused by unsafe handling of serialized data. It can be reached remotely, without logging in, and an attacker who exploits it could potentially run code or otherwise take over the affected site.
Written by a model
Original description
Deserialization of Untrusted Data vulnerability in Tribulant Software Newsletters newsletters-lite allows Object Injection.This issue affects Newsletters: from n/a through 4.18.2.
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-129039 (WordPress Newsletters plugin <= 4.18.2 - PHP Object 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-129039 (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):
- Tribulant Software Newsletters plugin version 4.18.2 or earlier (vulnerable versions <= 4.18.2) (source: https://patchstack.com/database/wordpress/plugin/newsletters-lite/vulnerability/wordpress-newsletters-plugin-4-18-2-php-object-injection-vulnerability-2?_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-129039 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129039 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-php-object-injection-vulnerability-2?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-129039
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-129039
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-129039"}.Affected versions
- newsletters-litefixed in 4.18.3 · through 4.18.2
cve.now Index
- 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.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129039 |
| Record | NVD · CVE-2026-129039 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/newsletters-lite/vulnerability/wordpress-newsletters-plugin-4-18-2-php-object-injection-vulnerability-2?_s_id=cve |
Questions about CVE-2026-129039
Is CVE-2026-129039 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 does not safely handle serialized data it processes, so an attacker can manipulate how the site processes data to run harmful actions on the server.
Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-129039?
newsletters-lite: through 4.18.2 (fixed in 4.18.3).
Source: cve.now feed data
Am I affected, and how do I check?
Tribulant Software's Newsletters plugin for WordPress, version 4.18.2 and earlier, is affected. To check, look at the plugin version shown on the WordPress Plugins screen or in the plugin's readme file.
Source: patchstack.com, cve.org
How do I fix CVE-2026-129039?
Update the Newsletters plugin to version 4.18.3 or later, which is the listed fixed version.
Source: patchstack.com, cve.org
Related
- CVE-2026-94075WordPress Newsletters plugin <= 4.18.1 - PHP Object Injection vulnerability
- CVE-2025-67911WordPress Newsletters plugin <= 4.11 - PHP Object Injection vulnerability
- CVE-2026-116863WordPress Newsletters plugin <= 4.18.2 - Cross Site Request Forgery (CSRF) vulnerability
- CVE-2026-129043WordPress Newsletters plugin <= 4.18.2 - SQL Injection vulnerability
- CVE-2026-111402WordPress Newsletters plugin <= 4.18.1 - SQL Injection vulnerability
- CVE-2026-119512WordPress Newsletters plugin <= 4.18.2 - PHP Object Injection vulnerability
No corrections so far. Something wrong on this page? Report an error.