# CVE-2025-13051: Path traversal in ABP and AES

> Attackers can execute arbitrary code with LocalSystem privileges by planting malicious DLLs in writable service directories, requiring a service restart.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** GHSA-4vm6-5mqx-h27m

## What is CVE-2025-13051?

CVE-2025-13051 is a critical path traversal vulnerability in ASUSTOR ABP and AES, published on 19 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When the service of ABP and AES is installed in a directory writable by non-administrative users, an attacker can replace or plant a DLL with the same name as one loaded by the service. Upon service restart, the malicious DLL is loaded and executed under the LocalSystem account, resulting in unauthorized code execution with elevated privileges.
This issue affects ABP and AES: from ABP 2.0 through 2.0.7.9050, from AES 1.0 through 1.0.6.8290.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2025-13051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13051 is a critical path traversal vulnerability in ASUSTOR ABP and AES, published on 19 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13051 in the wild and no public exploit code.

Affected product: ASUSTOR ABP and AES. 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-13051/ (Markdown: https://insights.sbomify.com/CVE-2025-13051/index.md)
```

## Sources

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

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