# CVE-2025-44177: Path traversal in n/a

> An unauthenticated attacker can remotely read arbitrary files on the underlying OS via directory traversal in the Protop server software.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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:** 9 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-98m5-g5jg-4wf7

## What is CVE-2025-44177?

CVE-2025-44177 is a high-severity path traversal vulnerability in n/a, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A directory traversal vulnerability was discovered in White Star Software Protop version 4.4.2-2024-11-27, specifically in the /pt3upd/ endpoint. An unauthenticated attacker can remotely read arbitrary files on the underlying OS using encoded traversal sequences.

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

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

It affects 1 product.


Products: Wss Protop.

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

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

## Is CVE-2025-44177 being exploited?

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

Public exploit code:

- White Star Software Protop 4.4.2-2024-11-27 - Local File Inclusion (LFI) (exploitdb)
- White Star Software ProTop - Directory Traversal (nuclei): http/cves/2025/CVE-2025-44177.yaml

## Fix prompt for AI coding agents

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

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

## Sources

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

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