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

> Attackers can delete arbitrary files via directory traversal in SUCMS admin template, potentially causing service disruption.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 27 Feb 2025
- **Updated:** 4 Mar 2025
- **Also known as:** GHSA-6prj-x8h3-vcvh

## What is CVE-2025-25759?

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

### Official description

An issue in the component admin_template.php of SUCMS v1.0 allows attackers to execute a directory traversal and arbitrary file deletion via a crafted GET request.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Sucms Project Sucms.

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

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

## Is CVE-2025-25759 being exploited?

There is no known exploitation of CVE-2025-25759 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-25760](https://insights.sbomify.com/CVE-2025-25760/): Server-side request forgery in n/a (high 7.5)
- [CVE-2024-13194](https://insights.sbomify.com/CVE-2024-13194/): Sucms admin_members.php sql injection (medium 5.3)
- [CVE-2023-2768](https://insights.sbomify.com/CVE-2023-2768/): Sucms cross site scripting (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25759 is a high-severity path traversal vulnerability in n/a, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25759 in the wild and no public exploit code.

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-25759/ (Markdown: https://insights.sbomify.com/CVE-2025-25759/index.md)
```

## Sources

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

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