CVE-2026-75962 json
Post SMTP <= 4.0.1 - Unauthenticated Stored DOM-Based Cross-Site Scripting via 'user_email' Parameter (Multisite Registration → Failed Email Log)
published last mo. modified last mo. also EUVD-2026-92961
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 20%
- public exploits
- 0
- none known
Summary
The Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'user_email' parameter in all versions up to, and including, 4.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable without authentication on WordPress Multisite installations with public registration enabled, as WordPress accepts email addresses containing numeric HTML character references that Post SMTP's stricter validator rejects, persisting the attacker-controlled address verbatim to the email log via the failed-send exception message.
Is CVE-2026-75962 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- saadiqbal Post SMTP – Complete Email Delivery and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/accac3da-0318-4e79-a163-ed9ff2af692b?source=cve
- plugins.trac.wordpress.org /browser/post-smtp/tags/3.9.5/Postman/PostmanWpMail.php#L374
- plugins.trac.wordpress.org /browser/post-smtp/tags/3.9.5/script/postman-email-logs.js#L711
- plugins.trac.wordpress.org /browser/post-smtp/tags/3.9.5/Postman/PostmanEmailLogs.php#L538
- plugins.trac.wordpress.org /browser/post-smtp/tags/3.9.5/Postman/Postman-Email-Log/PostmanEmailLogService.php#L215
- plugins.trac.wordpress.org /browser/post-smtp/tags/3.9.5/Postman/Postman-Mail/PostmanEmailAddress.php#L63
- plugins.trac.wordpress.org /changeset?reponame=&new=3711079%40post-smtp%2Ftags%2F4.0.2&old=3664536%40post-smtp%2Ftags%2F4.0.1
- plugins.trac.wordpress.org /changeset/3711068/post-smtp/trunk/Postman/Postman-Email-Log/PostmanEmailLogService.php
Sources
- CVE List CVE-2026-75962
- NVD CVE-2026-75962
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.