CVE-2025-41040: appRain CMF · XSS or 'Cross-site Scripting'
Affects appRain CMFSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| appRain appRain CMF | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Immediately review and restrict access to the /apprain/developer/language/lipsum.xml endpoint to trusted administrators only, ideally behind VPN or IP whitelisting. 2) Apply strict input validation and output encoding on all affected parameters ('data[code]', 'data[lang][0][key]', 'data[lang][0][value]', 'data[lang][1][key]', 'data[title]') to neutralize script injection vectors, using context-aware encoding (e.g., HTML entity encoding). 3) Monitor and audit user input logs for suspicious or anomalous entries indicative of attempted XSS payloads. 4) Enforce strong authentication and session management controls to reduce risk from compromised accounts. 5) Deploy Content Security Policy (CSP) headers to restrict execution of unauthorized scripts in browsers. 6) Conduct user awareness training to prevent social engineering attacks that could lead to account compromise. 7) Track vendor updates and apply patches promptly once available. 8) Consider implementing Web Application Firewalls (WAF) with rules targeting XSS payload patterns specific to appRain CMF. These tailored actions go beyond generic advice by focusing on the vulnerable parameters and access controls specific to this product and version.
Description
A vulnerability has been discovered in appRain CMF version 4.0.5, consisting of a stored authenticated XSS due to a lack of proper validation of user input, through the 'data[code]', 'data[lang][0][key]', 'data[lang][0][value]', 'data[lang][1][key]' and 'data[title]' parameters in /apprain/developer/language/lipsum.xml.