Stored XSS via unvalidated static-page name
Published Sep 4, 2025 · Updated Sep 4, 2025
Stored XSS in appRain CMF 4.0.5 allows remote authenticated users to run script in another user's browser through a static-page name. The static-page creation handler accepts data[Page][name] without proper validation and stores it for later rendering as page content. An authenticated attacker must create a static page, and exploitation occurs when another user loads the stored value, exposing that browser session to script-driven read or write actions.
Summary
What happened
Stored XSS in appRain CMF 4.0.5 allows remote authenticated users to run script in another user's browser through a static-page name. The static-page creation handler accepts data[Page][name] without proper validation and stores it for later rendering as page content. An authenticated attacker must create a static page, and exploitation occurs when another user loads the stored value, exposing that browser session to script-driven read or write actions.
The record
- CVE
- CVE-2025-41044
- Published
- Sep 4, 2025
- Updated
- Sep 4, 2025
- Vendor
- appRain
- Product
- appRain CMF
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 4, 2025CVE publishedPublication date reported by the CVE source.
- Sep 4, 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=4.0.5
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