SMSEagle before 6.11 allows reflected XSS via a username or contact phone number.
Priority LOW 24CWE-79Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-79.
Summary
SMSEagle before 6.11 allows reflected XSS via a username or contact phone number.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00191 8th percentileScored 2026-11-07
Fix Fixed SMSEagle (SMSEagle): 6.11
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA SMSEagle (SMSEagle) Fixed in 6.11
Timeline
- 2026-10-02 Threatist record created from CVE-2025-59715
- 2026-10-03 Alias added: GHSA-cqj4-f3cq-m6pj
References
More Smseagle vulnerabilities
- TI-2024-24897 A stored Cross-Site Scripting (XSS) vulnerability has been identified in SMSEagle… CVSS 3.1MEDIUM 6.1
Sources
- CVE-2025-59715 · CVE Program
- CVE-2025-59715 · NVD
- FIRST EPSS
- GHSA-cqj4-f3cq-m6pj · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences