CVE-2026-39498: YayMail (WordPress plugin) · Deserialization of Untrusted Data
Affects YayMail (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| YeeaddonsYayMail | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict shop manager privileges to trusted users only and monitor for suspicious activity related to deserialization processes. Avoid importing or processing untrusted serialized data where possible.
Description
A high-severity vulnerability (CVE-2026-39498) exists in Yeeaddons YayMail versions up to and including 4.3.3. It involves PHP Object Injection due to deserialization of untrusted data, allowing a shop manager level user to potentially execute malicious actions. The vulnerability has a CVSS score of 7.2, indicating significant impact on confidentiality, integrity, and availability. No official patch or remediation guidance is currently provided by the vendor.