FreshRSS up to 1.26.x Allow API api/query.php history.replaceState cross site scripting

Summaryinfo

A vulnerability, which was classified as problematic, has been found in FreshRSS up to 1.26.x. Affected by this issue is the function history.replaceState of the file api/query.php of the component Allow API. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2025-59948. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in FreshRSS up to 1.26.x and classified as problematic. This issue affects the function history.replaceState of the file api/query.php of the component Allow API. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

FreshRSS is a free, self-hostable RSS aggregator. Versions 1.26.3 and below do not sanitize certain event handler attributes in feed content, so by finding a page that renders feed entries without CSP, it is possible to execute an XSS payload. The Allow API access authentication setting needs to be enabled by the instance administrator beforehand for the attack to work as it relies on api/query.php. An account takeover is possible by sending a change password request via the XSS payload / setting UserJS for persistence / stealing the autofill password / displaying a phishing page with a spoofed URL using history.replaceState() If the victim is an administrator, the attacker can also perform administrative actions. This issue is fixed in version 1.27.0.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-59948 since 09/23/2025. The exploitation is known to be difficult. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

By approaching the search of inurl:api/query.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 1.27.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 7df6c201f2e6a6521d20718dfd8d9794c7437d1f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• FreshRSS

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26

License

• open-source

Website

• Product: https://github.com/FreshRSS/FreshRSS/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion