# CVE-2024-8725: Advanced File Manager <= 5.2.8 - Authenticated (Subscriber+) Limited File Upload

> Authenticated subscribers can upload malicious CSS/JS files to arbitrary directories, leading to stored XSS and potential code execution.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 26 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gqqx-m28r-fmjj

## What is CVE-2024-8725?

CVE-2024-8725 is a medium-severity vulnerability in saadiqbal Advanced File Manager – Ultimate File Manager for WordPress And Document Library Solution, published on 26 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple plugins and/or themes for WordPress are vulnerable to Limited File Upload in various versions. This is due to a lack of proper checks to ensure lower-privileged roles cannot upload .css and .js files to arbitrary directories. This makes it possible for authenticated attackers, with Subscriber-level access and above, and granted permissions by an administrator, to upload .css and .js files to any directory within the WordPress root directory, which could lead to Stored Cross-Site Scripting. The Advanced File Manager Shortcodes plugin must be installed to exploit this vulnerability.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Advancedfilemanager Advanced File Manager.

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

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

## Is CVE-2024-8725 being exploited?

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

## Other vulnerabilities in saadiqbal Advanced File Manager – Ultimate File Manager for WordPress And Document Library Solution

- [CVE-2024-13333](https://insights.sbomify.com/CVE-2024-13333/): Advanced File Manager 5.2.12 - 5.2.13 - Authenticated (Subscriber+) Arbitrary File Upload (high 7.5)
- [CVE-2024-11391](https://insights.sbomify.com/CVE-2024-11391/): Advanced File Manager <= 5.2.10 - Authenticated (Subscriber+) Arbitrary File Upload (high 7.5)
- [CVE-2024-8126](https://insights.sbomify.com/CVE-2024-8126/): Advanced File Manager <= 5.2.8 - Authenticated (Subscriber+) Arbitrary File Upload (high 7.5)
- [CVE-2024-5598](https://insights.sbomify.com/CVE-2024-5598/): Advanced File Manager <= 5.2.4 - Sensitive Information Exposure via Directory Listing (high 7.5)
- [CVE-2024-8704](https://insights.sbomify.com/CVE-2024-8704/): Advanced File Manager <= 5.2.8 - Authenticated (Administrator+) Local JavaScript File Inclusion via fma_locale (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8725 is a medium-severity vulnerability in saadiqbal Advanced File Manager – Ultimate File Manager for WordPress And Document Library Solution, published on 26 Sep 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-8725 in the wild and no public exploit code.

Affected product: saadiqbal Advanced File Manager – Ultimate File Manager for WordPress And Document Library Solution. 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-8725/ (Markdown: https://insights.sbomify.com/CVE-2024-8725/index.md)
```

## Sources

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

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