Unauthenticated stored XSS via unsanitized device header
Published Jan 3, 2024 · Updated Apr 8, 2026
Stored XSS in Fullworks Plugins Post SMTP 2.8.7 and earlier allows remote attackers to inject scripts through the device header. The connect_app() function stores the header without sanitization, and section() echoes the saved device value without output escaping. No authentication is required to plant the payload, but an administrator must open the mobile application settings page for the script to execute in that browser context.
Summary
What happened
Stored XSS in Fullworks Plugins Post SMTP 2.8.7 and earlier allows remote attackers to inject scripts through the device header. The connect_app() function stores the header without sanitization, and section() echoes the saved device value without output escaping. No authentication is required to plant the payload, but an administrator must open the mobile application settings page for the script to execute in that browser context.
The record
- CVE
- CVE-2023-7027
- Published
- Jan 3, 2024
- Updated
- Apr 8, 2026
- Vendor
- Fullworks Plugins
- Product
- Post SMTP
- Classifications
- CWE-79, T1190, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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 <=2.8.7
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