# CVE-2025-10213: DLL search path hijacking vulnerability

> Local attackers can execute arbitrary code via DLL hijacking in UPDF by placing a malicious file in a specific directory.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-4pvg-877c-6rg9

## What is CVE-2025-10213?

CVE-2025-10213 is a high-severity vulnerability in UPDF, published on 10 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

DLL search path hijacking vulnerability in the UPDF.exe executable for Windows version 1.8.5.0 allows attackers with local access to execute arbitrary code by placing a dxtn.dll file of their choice in the 'C:\Users\<user>\AppData\Local\Microsoft\WindowsApps\' directory, which could lead to arbitrary code execution and persistence.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Updf Updf.

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

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

## Is CVE-2025-10213 being exploited?

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

## Other vulnerabilities in UPDF

- [CVE-2025-10214](https://insights.sbomify.com/CVE-2025-10214/): DLL search path hijacking vulnerability (high 7.0)
- [CVE-2025-10215](https://insights.sbomify.com/CVE-2025-10215/): DLL search path hijacking vulnerability (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10213 is a high-severity vulnerability in UPDF, published on 10 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-10213 in the wild and no public exploit code.

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

## Sources

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

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