Stored XSS via unsanitized email attachments
Published Jan 13, 2026 · Updated Jan 13, 2026
Stored XSS in MailHog 1.0.1 allows remote attackers to execute script in an operator's browser through a crafted email attachment. The web UI renders script-bearing attachment content as active browser content instead of neutralizing it. An operator must open the captured message; the resulting same-origin script can call the HTTP API, including deleting stored messages.
Summary
What happened
Stored XSS in MailHog 1.0.1 allows remote attackers to execute script in an operator's browser through a crafted email attachment. The web UI renders script-bearing attachment content as active browser content instead of neutralizing it. An operator must open the captured message; the resulting same-origin script can call the HTTP API, including deleting stored messages.
The record
- CVE
- CVE-2022-50908
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- MailHog
- Product
- MailHog
- Classifications
- CWE-79, T1204.002
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Mailhog 1.0.1 Stored Cross-Site Scripting proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo