# CVE-2025-54591: FreshRSS: Unauthenticated users can view default user's information

> Unauthenticated attackers can view sensitive feed and tag information of default admin users due to missing access checks in specific endpoints.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-jf4v-f8p2-8xvq

## What is CVE-2025-54591?

CVE-2025-54591 is a high-severity missing authorization vulnerability in FreshRSS, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreshRSS is a free, self-hostable RSS aggregator. Versions 1.26.3 and below expose information about feeds and tags of default admin users, due to lack of access checking in the FreshRSS_Auth::hasAccess() function used by some of the tag/feed related endpoints. FreshRSS controllers usually have a defined firstAction() method with an override to make sure that every action requires access. If one doesn't, then every action has to check for access manually, and certain endpoints use neither the firstAction() method, or do they perform a manual access check. This issue is fixed in version 1.27.0.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Freshrss Freshrss.

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

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

## Is CVE-2025-54591 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54591 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-58173](https://insights.sbomify.com/CVE-2025-58173/): FreshRSS vulnerable to authenticated RCE via path traversal inside include() (high 7.4)
- [CVE-2025-54593](https://insights.sbomify.com/CVE-2025-54593/): FreshRSS is vulnerable to RCE attacks by authenticated admin (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54591 is a high-severity missing authorization vulnerability in FreshRSS, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54591 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-54591/ (Markdown: https://insights.sbomify.com/CVE-2025-54591/index.md)
```

## Sources

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

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