# CVE-2025-8357: Media Library Assistant <= 3.27 - Authenticated (Author+) Limited File Deletion

> Authenticated attackers with Author-level access can delete arbitrary files in the uploads directory due to insufficient capability checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v45q-4525-5g76

## What is CVE-2025-8357?

CVE-2025-8357 is a medium-severity missing authorization vulnerability in dglingren Media Library Assistant, published on 19 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Media Library Assistant plugin for WordPress is vulnerable to arbitrary file deletion in the /wp-content/uploads directory due to insufficient file path validation and user capability checking in the _process_mla_download_file function in all versions up to, and including, 3.27. This makes it possible for authenticated attackers, with Author-level access and above, to delete arbitrary files on the server from the /wp-content/uploads/ directory.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-8357 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8357 is a medium-severity missing authorization vulnerability in dglingren Media Library Assistant, published on 19 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8357 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-8357/ (Markdown: https://insights.sbomify.com/CVE-2025-8357/index.md)
```

## Sources

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

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