# CVE-2025-58173: FreshRSS vulnerable to authenticated RCE via path traversal inside include()

> Authenticated attackers can exploit path traversal in language settings to gain admin access and execute arbitrary code via malicious database configurations.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **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:** 15 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-6c8h-w3j5-j293

## What is CVE-2025-58173?

CVE-2025-58173 is a high-severity path traversal vulnerability in FreshRSS, published on 15 Dec 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. In versions 1.23.0 through 1.27.0, using a path traversal inside the `language` user configuration parameter, it's possible to call `install.php` and perform various administrative actions as an unprivileged user. These actions include logging in as the admin, creating a new admin user, or set the database to an attacker-controlled MySQL server and abuse it to execute code in FreshRSS by setting malicious feed `curl_params` inside the `feed` table. Version 1.27.1 fixes the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Freshrss Freshrss.

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

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

## Is CVE-2025-58173 being exploited?

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

What it is: CVE-2025-58173 is a high-severity path traversal vulnerability in FreshRSS, published on 15 Dec 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-58173 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-58173/ (Markdown: https://insights.sbomify.com/CVE-2025-58173/index.md)
```

## Sources

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

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