# CVE-2024-8704: Advanced File Manager <= 5.2.8 - Authenticated (Administrator+) Local JavaScript File Inclusion via fma_locale

> Administrators can exploit a local file inclusion vulnerability to execute arbitrary PHP code and access sensitive data on the server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-p9fh-v6cv-cj9f

## What is CVE-2024-8704?

CVE-2024-8704 is a high-severity path traversal vulnerability in saadiqbal Advanced File Manager – Ultimate File Manager for WordPress And Document Library Solution, published on 26 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Advanced File Manager plugin for WordPress is vulnerable to Local JavaScript File Inclusion in all versions up to, and including, 5.2.8 via the 'fma_locale' parameter. This makes it possible for authenticated attackers, with Administrator-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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

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

It affects 1 product.


Products: Advancedfilemanager Advanced File Manager.

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

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

## Is CVE-2024-8704 being exploited?

There is no known exploitation of CVE-2024-8704 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-8725](https://insights.sbomify.com/CVE-2024-8725/): Advanced File Manager <= 5.2.8 - Authenticated (Subscriber+) Limited File Upload (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8704 is a high-severity path traversal vulnerability in saadiqbal Advanced File Manager – Ultimate File Manager for WordPress And Document Library Solution, published on 26 Sep 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8704 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-8704/ (Markdown: https://insights.sbomify.com/CVE-2024-8704/index.md)
```

## Sources

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

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