Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Newsletters <4.15
-
DeliverySubmit crafted serialized object via public form
-
ExploitServer deserializes untrusted PHP object
-
ExecutionBundled POP gadget chain triggers file write
-
PersistWrite PHP webshell to webroot
-
ImpactExecute arbitrary code on server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target run the Newsletters plugin at a version before 4.15 and that the plugin's public-facing form (the subscriber/subscription input handler) be reachable and accepting submissions - this is the default deployment state for a plugin whose purpose is public newsletter sign-up. No authentication is needed (PR:N) and no user interaction is required (UI:N). The main limiting factor is attack complexity (AC:H): a reliable payload must match the plugin's bundled POP gadget chain, and success depends on the specific vulnerable version being installed and PHP being able to write to a target path; the public POC substantially reduces this barrier. No non-standard configuration is otherwise required. |
| Impact | The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (8.1, High) reflects a network-reachable, unauthenticated (PR:N) flaw with no user interaction but high attack complexity (AC:H) and full CIA impact - consistent with a deserialization RCE where crafting/aligning the object payload against a specific plugin version is non-trivial. Publicly available exploit code raises the practical risk materially, since the AC:H barrier is largely eliminated once a working payload is published. No EPSS score was provided, so probabilistic exploitation likelihood cannot be quantified, and no SSVC decision data or KEV listing is present - meaning there is no confirmation of active exploitation, only proven exploitability. On balance this is a genuine high priority for any environment running the plugin: unauthenticated RCE with a bundled gadget chain and a public POC is a strong candidate for opportunistic mass-scanning, even though widespread active exploitation is not yet evidenced. |
| Exploit ScenarioDerived | An attacker locates a WordPress site running Newsletters below 4.15, then submits a crafted serialized PHP object through the plugin's public subscription form with no account or authentication required. When the server deserializes the input, the plugin's bundled gadget chain fires, writing a PHP webshell into the webroot and yielding remote code execution; a public POC for this exact flow is available via WPScan, lowering the practical difficulty despite the CVSS AC:H rating. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 14, 2026
Unauthenticated PHP object injection in the Newsletters WordPress plugin before 4.15 lets remote attackers deserialize attacker-controlled data submitted through a public-facing form, then leverage a property-oriented gadget chain bundled inside the plugin itself to write arbitrary files and achieve remote code execution on the host. Publicly available exploit code exists (published via WPScan), though there is no public exploit identified as being used in active attacks and the flaw is not listed in CISA KEV. The self-contained gadget chain removes the usual dependency on third-party gadgets, making reliable exploitation notably more achievable than typical POI bugs.
RemediationAI
Vendor-released patch: version 4.15 - upgrade the Newsletters plugin to 4.15 or later immediately, as the fix eliminates the unsafe deserialization of public form input. Consult the WPScan advisory at https://wpscan.com/vulnerability/e4c44105-f43d-4dff-8487-7d8ae2691c4e/ for details. If patching cannot be done at once, apply compensating controls: deactivate the Newsletters plugin entirely (removes the vulnerable code path but disables all newsletter/subscription functionality), or place a WAF rule in front of the site to block requests to the plugin's public form endpoints containing serialized PHP payloads (patterns such as leading 'O:' or 'a:' object/array markers) - noting WAF signatures can be bypassed with obfuscated payloads and may produce false positives on legitimate submissions. Additionally restrict web-server write permissions on the WordPress directory to blunt the arbitrary-file-write primitive, accepting that this can break other plugins that legitimately write files.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Newsletters plugin for WordPress (CPE cpe:2.3:a:unknown:newsletters), a subscriber/email-campaign management extension. The root cause is CWE-502 (Deserialization of Untrusted Data): user input captured by a public form is passed to PHP's unserialize() without validation or an allow-list, so an attacker can supply a serialized PHP object of a class of their choosing. Exploitation is elevated from mere object instantiation to full RCE because the plugin ships a POP (property-oriented programming) gadget chain - magic methods such as __wake up/__destruct across the plugin's own classes that, when triggered during deserialization, chain into filesystem-write primitives and ultimately code execution. Because the gadgets are bundled with the plugin, the attack does not depend on the presence of vulnerable gadgets in WordPress core or other plugins.
Know when Newsletters gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable, unauthenticated public form (AV:N/PR:N/UI:N); AC:H because a version-specific POP payload must be crafted; deserialization RCE yields full C/I/A impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Newsletters WordPress plugin before 4.15 does not prevent deserialization of untrusted input that is stored through a public form, allowing unauthenticated attackers to inject a PHP object and, via a property-oriented gadget chain bundled with the Newsletters WordPress plugin before 4.15, write arbitrary files and execute code on the server.
Executive ViewAI
The Newsletters WordPress plugin prior to version 4.15 contains a critical remote code execution vulnerability allowing unauthenticated attackers to inject and execute arbitrary code through public-facing forms. Publicly available exploit code exists (published via WPScan), creating immediate risk for any organization running this plugin. Website compromise, data exfiltration, and malware deployment threaten both customer data and operational continuity.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
More in Newsletters
View allwp-admin/admin-ajax.php?action=newsletters_exportmultiple in the Tribulant Newsletters plugin before 4.6.19 for WordPres
Server-Side Request Forgery (SSRF) in the Newsletters WordPress plugin before 4.16 allows unauthenticated remote attacke
PHP object injection in the Newsletters WordPress plugin (all versions before 4.16) permits unauthenticated remote attac
Unauthenticated time-based SQL injection in the Newsletters plugin for WordPress (versions up to and including 4.13) all
PHP object injection in Tribulant Newsletters, the WordPress plugin newsletters-lite, through version 4.18.1 allows remo
Cross-site request forgery in the Tribulant Newsletters WordPress plugin (newsletters-lite) through version 4.18.2 allow
Cross-Site Request Forgery in the Newsletters WordPress plugin (versions before 4.17) enables unauthenticated attackers
The Tribulant Newsletters plugin before 4.6.19 for WordPress allows XSS via the wp-admin/admin-ajax.php?action=newslette
SQL injection in the Tribulant Newsletters WordPress plugin (newsletters-lite) through version 4.18.1 allows unauthentic
Authentication bypass in the Newsletters WordPress plugin (all versions before 4.16) allows remote unauthenticated attac
Predictable API key generation in the Newsletters WordPress plugin (versions before 4.17) enables unauthenticated networ
The Newsletters plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 4.9.9.2
EUVD-2026-43627
GHSA-cxqr-jhpf-63mm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB