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

> Remote attackers can read arbitrary files via directory traversal in SNMP Web Pro's upload.cgi due to lack of input validation.

- **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:** 9 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** GHSA-22gf-2q7p-998g

## What is CVE-2025-65287?

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

### Official description

An unauthenticated directory traversal vulnerability in cgi-bin/upload.cgi in SNMP Web Pro 1.1 allows a remote attacker to read arbitrary files. The CGI concatenates the user-supplied params directly onto the base path (/var/www/files/userScript/) using memcpy + strcat without validation or canonicalization, enabling ../ sequences to escape the intended directory. The download branch also echoes the unsanitized params into Content-Disposition, introducing header-injection risk.

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

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

It affects 1 product.


Products: Cdpenergy Snmp Web Pro Firmware.

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

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

## Is CVE-2025-65287 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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