# CVE-2026-11974: Media folder Addon < 4.1.7 - Unauthenticated Arbitrary File Download

> Unauthenticated attackers can download arbitrary files via path traversal in the Media folder Addon plugin, exposing sensitive server data.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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:** 29 Jul 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-fj8r-hgww-qgmw

## What is CVE-2026-11974?

CVE-2026-11974 is a high-severity path traversal vulnerability in Unknown wp-media-folder-addon, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The wp-media-folder-addon WordPress plugin before 4.1.7 does not validate a user-supplied parameter before using it in a file read operation in two AJAX actions available to unauthenticated users, leading to Arbitrary File Disclosure and Server-Side Request Forgery on sites where a cloud storage connection has been configured. This is an incomplete fix of CVE-2026-9690, whose patch hardened only one of the affected cloud-storage handlers and left the others unpatched.

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

## Which versions are affected by CVE-2026-11974?


## How do I fix CVE-2026-11974?

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

## Is CVE-2026-11974 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11974 and fix it if it is affected.

What it is: CVE-2026-11974 is a high-severity path traversal vulnerability in Unknown wp-media-folder-addon, published on 29 Jul 2026. 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-2026-11974 in the wild and no public exploit code.

Affected product: Unknown wp-media-folder-addon. 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-2026-11974/ (Markdown: https://insights.sbomify.com/CVE-2026-11974/index.md)
```

## Sources

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

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