# CVE-2024-25907: WordPress WP Media folder plugin <= 5.7.2 - Plugin Settings Change vulnerability

> An attacker can modify WP Media folder plugin settings without proper authorization, potentially altering site behavior.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 21 Mar 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-j66j-8jmr-p8r5

## What is CVE-2024-25907?

CVE-2024-25907 is a medium-severity missing authorization vulnerability in JoomUnited WP Media folder, published on 21 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in JoomUnited WP Media folder.This issue affects WP Media folder: from n/a through 5.7.2.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-25907 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25907 is a medium-severity missing authorization vulnerability in JoomUnited WP Media folder, published on 21 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-25907 in the wild and no public exploit code.

Affected product: JoomUnited WP Media folder. 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-25907/ (Markdown: https://insights.sbomify.com/CVE-2024-25907/index.md)
```

## Sources

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

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