# CVE-2025-46341: Privilege escalation via SSRF when using HTTP auth

> An attacker with an account can exploit SSRF in FreshRSS to impersonate users and escalate privileges when HTTP auth via reverse proxy is enabled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2025
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-w3m8-wcf4-h8vm

## What is CVE-2025-46341?

CVE-2025-46341 is a high-severity server-side request forgery vulnerability in FreshRSS, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, when the server is using HTTP auth via reverse proxy, it's possible to impersonate any user either via the `Remote-User` header or the `X-WebAuth-User` header by making specially crafted requests via the add feed functionality and obtaining the CSRF token via XPath scraping. The attacker has to know the IP address of the proxied FreshRSS instance and the admin's username, while also having an account on the instance. An attacker can send specially crafted requests in order to gain unauthorized access to internal services. This can also lead to privilege escalation like in the demonstrated scenario, although users that have setup OIDC are not affected by privilege escalation. Version 1.26.2 contains a patch for the issue.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Freshrss Freshrss.

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

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

## Is CVE-2025-46341 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46341 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-46341 and fix it if it is affected.

What it is: CVE-2025-46341 is a high-severity server-side request forgery vulnerability in FreshRSS, published on 4 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46341 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-46341/ (Markdown: https://insights.sbomify.com/CVE-2025-46341/index.md)
```

## Sources

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

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