Stored XSS via unescaped email-log output
Published Feb 22, 2025 · Updated Jun 4, 2026
Stored XSS in YayCommerce SMTP for Sendinblue – YaySMTP 1.2 and earlier allows remote attackers to execute scripts via email logs. The email-log path stores attacker-controlled message fields without sufficient sanitization and renders them in log pages without context-appropriate escaping. No authentication is required to seed a malicious log entry, but a user must open the affected page; execution occurs in that viewer's browser.
Summary
What happened
Stored XSS in YayCommerce SMTP for Sendinblue – YaySMTP 1.2 and earlier allows remote attackers to execute scripts via email logs. The email-log path stores attacker-controlled message fields without sufficient sanitization and renders them in log pages without context-appropriate escaping. No authentication is required to seed a malicious log entry, but a user must open the affected page; execution occurs in that viewer's browser.
The record
- CVE
- CVE-2025-0953
- Published
- Feb 22, 2025
- Updated
- Jun 4, 2026
- Vendor
- YayCommerce
- Product
- SMTP for Sendinblue – YaySMTP
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2025CVE publishedPublication date reported by the CVE source.
- Jun 4, 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=0 <=1.2
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
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