Stored script execution via unsanitized email logs
Published Feb 19, 2025 · Updated Feb 19, 2025
Stored XSS in YayCommerce YaySMTP 2.4.9 through 2.6.2 allows remote attackers to inject scripts through stored email content. The email-log rendering path in includes/Helper/Utils.php outputs stored message content without wp_kses_post sanitization or adequate escaping. No authentication is required to supply crafted content; the script executes when an administrator or another user opens the affected log page.
Summary
What happened
Stored XSS in YayCommerce YaySMTP 2.4.9 through 2.6.2 allows remote attackers to inject scripts through stored email content. The email-log rendering path in includes/Helper/Utils.php outputs stored message content without wp_kses_post sanitization or adequate escaping. No authentication is required to supply crafted content; the script executes when an administrator or another user opens the affected log page.
The record
- CVE
- CVE-2025-0916
- Published
- Feb 19, 2025
- Updated
- Feb 19, 2025
- Vendor
- YayCommerce
- Product
- YaySMTP
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record 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=2.4.9 <=2.6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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