CVE-2025-32015: FreshRSS · Cross-site Scripting
Affects FreshRSSSource CVE Database V5
Not known to be exploited · CVSS 6.7 Medium : upgrade to 1.26.2 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.26.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 4 Jun 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-25.
What to do
Upgrade freshrss/FreshRSS to 1.26.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfreshrss/FreshRSSpkg:github/freshrss/FreshRSSOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade all FreshRSS instances to version 1.26.2 or later to apply the official patch that corrects the sanitization flaw. Additionally, organizations should audit user account creation policies to ensure only trusted users can register or be granted access, reducing the likelihood of attacker account creation. Implementing strict input validation and content security policies (CSP) can help mitigate the impact of any residual XSS vulnerabilities. Monitoring logs for unusual feed submissions or script injection attempts can provide early detection of exploitation attempts. For critical environments, consider isolating FreshRSS instances within segmented network zones to limit potential lateral movement if compromise occurs. Regular backups of user data and configurations should be maintained to enable recovery in case of destructive attacks. Finally, educating users and administrators about the risks of malicious feeds and the importance of applying security updates promptly is essential.
Description
FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, HTML is sanitized improperly inside the `<iframe srcdoc>` attribute, which leads to cross-site scripting (XSS) by loading an attacker's UserJS inside `<script src>`. In order to execute the attack, the attacker needs to control one of the victim's feeds and have an account on the FreshRSS instance that the victim is using. An attacker can gain access to the victim's account by exploiting this vulnerability. If the victim is an admin it would be possible to delete all users (cause damage) or execute arbitrary code on the server by modifying the update URL using fetch() via the XSS. Version 1.26.2 contains a patch for the issue.