# CVE-2025-30387: Document Intelligence Studio On-Prem Elevation of Privilege Vulnerability

> An attacker can exploit a path traversal flaw in Azure AI Document Intelligence Studio to elevate privileges over the network.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-j6rm-rh5c-35fw

## What is CVE-2025-30387?

CVE-2025-30387 is a critical path traversal vulnerability in Microsoft Azure AI Document Intelligence Studio, published on 13 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper limitation of a pathname to a restricted directory ('path traversal') in Azure allows an unauthorized attacker to elevate privileges over a network.

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

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

It affects 1 product.


Products: Microsoft Azure Ai Document Intelligence Studio.

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

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

## Is CVE-2025-30387 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30387 is a critical path traversal vulnerability in Microsoft Azure AI Document Intelligence Studio, published on 13 May 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-30387 in the wild and no public exploit code.

Affected product: Microsoft Azure AI Document Intelligence Studio. 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-30387/ (Markdown: https://insights.sbomify.com/CVE-2025-30387/index.md)
```

## Sources

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

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