# CVE-2025-11738: Media Library Assistant <= 3.29 - Unauthenticated Limited File Read

> Unauthenticated attackers can read arbitrary AI, EPS, PDF, or PS files on the server via the Media Library Assistant plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 18 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-4xmm-w6fx-6vm3

## What is CVE-2025-11738?

CVE-2025-11738 is a medium-severity path traversal vulnerability in dglingren Media Library Assistant, published on 18 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Media Library Assistant plugin for WordPress is vulnerable to limited file reading in all versions up to, and including, 3.29 via the mla-stream-image.php file. This makes it possible for unauthenticated attackers to read the contents of arbitrary ai/eps/pdf/ps files on the server, which can contain sensitive information.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2025-11738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11738 is a medium-severity path traversal vulnerability in dglingren Media Library Assistant, published on 18 Oct 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-11738 in the wild and no public exploit code.

Affected product: dglingren Media Library Assistant. 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-11738/ (Markdown: https://insights.sbomify.com/CVE-2025-11738/index.md)
```

## Sources

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

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