# CVE-2019-25053: Path traversal in n/a

> Remote unauthenticated attackers can access files outside the web tree via a crafted URL in Sage FRP 1000.

- **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:** 27 Jan 2023
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-66vg-fp7f-57vg

## What is CVE-2019-25053?

CVE-2019-25053 is a high-severity path traversal vulnerability in n/a, published on 27 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability exists in Sage FRP 1000 before November 2019. This allows remote unauthenticated attackers to access files outside of the web tree via a crafted URL.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-25053?

It affects 1 product.


Products: Sage Sage Frp 1000.

## How do I fix CVE-2019-25053?

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

## Is CVE-2019-25053 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-48646](https://insights.sbomify.com/CVE-2024-48646/): File upload in n/a (high 8.1)
- [CVE-2024-48647](https://insights.sbomify.com/CVE-2024-48647/): Path traversal in n/a (high 7.2)
- [CVE-2024-48648](https://insights.sbomify.com/CVE-2024-48648/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25053 and fix it if it is affected.

What it is: CVE-2019-25053 is a high-severity path traversal vulnerability in n/a, published on 27 Jan 2023. 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-2019-25053 exists.

Affected product: n/a. 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-2019-25053/ (Markdown: https://insights.sbomify.com/CVE-2019-25053/index.md)
```

## Sources

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

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