# CVE-2025-59948: FreshRSS is vulnerable to XSS due to lack of CSP on HTML query page

> Attackers can execute XSS via unsanitized feed content to take over accounts or gain admin privileges if API access is enabled.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-rwhf-vjjx-gmm9

## What is CVE-2025-59948?

CVE-2025-59948 is a medium-severity cross-site scripting vulnerability in FreshRSS, published on 29 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-59948?

It affects 1 product.


Products: Freshrss Freshrss.

## How do I fix CVE-2025-59948?

No fix has been published for CVE-2025-59948 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59948 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59948 exists.

## Other vulnerabilities in FreshRSS

- [CVE-2025-54875](https://insights.sbomify.com/CVE-2025-54875/): FreshRSS: Unauthorized creation of admin user when registration is enabled (critical 9.8)
- [CVE-2025-54592](https://insights.sbomify.com/CVE-2025-54592/): FreshRSS has Incomplete Session Termination on Logout (high 8.8)
- [CVE-2025-62166](https://insights.sbomify.com/CVE-2025-62166/): FreshRSS has an IDOR which allows for viewing feeds of any user and leaking tokens (high 7.5)
- [CVE-2025-54591](https://insights.sbomify.com/CVE-2025-54591/): FreshRSS: Unauthenticated users can view default user's information (high 7.5)
- [CVE-2025-58173](https://insights.sbomify.com/CVE-2025-58173/): FreshRSS vulnerable to authenticated RCE via path traversal inside include() (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59948 and fix it if it is affected.

What it is: CVE-2025-59948 is a medium-severity cross-site scripting vulnerability in FreshRSS, published on 29 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59948 exists.

Affected product: FreshRSS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59948/ (Markdown: https://insights.sbomify.com/CVE-2025-59948/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59948
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59948
- OSV: https://osv.dev/vulnerability/CVE-2025-59948

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59948/
Summaries are generated and may contain mistakes; the official description above is the record.