CVE-2026-39498
Description
YayMail <= 4.3.3 is vulnerable to PHP Object Injection, allowing code execution via a crafted POP chain, impacting thousands of sites.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
YayMail <= 4.3.3 is vulnerable to PHP Object Injection, allowing code execution via a crafted POP chain, impacting thousands of sites.
Vulnerability
YayMail, a WordPress plugin, up to version 4.3.3 contains a PHP Object Injection vulnerability. The bug arises from insecure deserialization of user-supplied input, enabling injection of arbitrary PHP objects if a suitable POP (Property Oriented Programming) chain exists in the application or its dependencies. The vulnerable code path is reachable without authentication, requiring only that the plugin is activated.
Exploitation
An attacker can exploit this vulnerability by sending a crafted request containing a malicious serialized PHP object to the affected plugin endpoints. No prior authentication or special privileges are needed. The attack is expected to be used in mass-exploit campaigns, targeting thousands of WordPress sites regardless of traffic size [1].
Impact
Successful exploitation can lead to various severe outcomes, including arbitrary code execution, SQL injection, path traversal, denial of service, and other attacks, depending on the available POP chain [1]. The attacker may gain elevated privileges within the WordPress environment and potentially achieve full site compromise.
Mitigation
The vendor has released version 4.3.4, which fixes the vulnerability [1]. Users are strongly advised to update immediately. For Patchstack subscribers, a mitigation rule is available to block attacks until the update is applied [1]. Automatic updates can be enabled for vulnerable plugins [1].
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.