Skip to main content
Menu
CVEs

Tribulant Newsletters remote code execution via PHP object injection

CVE-2026-119512EUVD-2026-125418GHSA-XJX4-R2RV-WQ6FPublished November 13, 2026, updated

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.18.3
Who is exposed
Specific setups only

Summary

Tribulant Software's Newsletters plugin for WordPress (package newsletters-lite) contains a PHP object injection flaw caused by unsafe deserialization of untrusted data. An attacker with low-privilege access can exploit it remotely over the network, which could let them run code or take control of 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-119512 (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-119512 (entry last updated 2026-11-13):
Affected:
- Tribulant Software Newsletters: fixed in 4.18.3
Fixed versions: 4.18.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-119512 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119512 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?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-119512
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-119512
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-119512"}.

Affected versions

cve.now Index

18of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 8.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Public exploit activity

100%0Nov 13Nov 20
  • EPSS: 0.37%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

Questions about CVE-2026-119512

Is CVE-2026-119512 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?

This is a PHP Object Injection bug, which lets attackers manipulate how the site processes data so that harmful actions run on the server.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-119512?

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

Source: cve.now feed data

Am I affected, and how do I check?

Versions of the WordPress Newsletters plugin from the earliest release through 4.18.2 are affected. To check a site, look at the installed plugin version on the WordPress Plugins screen.

Source: patchstack.com, cve.org

How do I fix CVE-2026-119512?

Update the WordPress Newsletters plugin to 4.18.3 or later, the fixed version named in the vendor's guidance.

Source: patchstack.com, cve.org

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