# CVE-2024-21325: Microsoft Printer Metadata Troubleshooter Tool Remote Code Execution Vulnerability

> An attacker can execute arbitrary code via untrusted search path in the Microsoft Printer Metadata Troubleshooter Tool.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-f7xv-mwmj-x7p9

## What is CVE-2024-21325?

CVE-2024-21325 is a high-severity path traversal vulnerability in Microsoft Printer Metadata Troubleshooter Tool, published on 9 Jan 2024. 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

Microsoft Printer Metadata Troubleshooter Tool Remote Code Execution Vulnerability

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2024-21325?

It affects 1 product.


Products: Microsoft Printer Metadata Troubleshooter Tool.

## How do I fix CVE-2024-21325?

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

## Is CVE-2024-21325 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21325 and fix it if it is affected.

What it is: CVE-2024-21325 is a high-severity path traversal vulnerability in Microsoft Printer Metadata Troubleshooter Tool, published on 9 Jan 2024. 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-2024-21325 in the wild and no public exploit code.

Affected product: Microsoft Printer Metadata Troubleshooter Tool. 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-2024-21325/ (Markdown: https://insights.sbomify.com/CVE-2024-21325/index.md)
```

## Sources

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

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