# CVE-2026-6382: Multiple elFinder Plugins - Authenticated OS Command Injection

> Authenticated attackers can execute arbitrary OS commands via image operations in multiple WordPress file manager plugins if ImageMagick CLI is available.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-jr7f-4jpg-mh92

## What is CVE-2026-6382?

CVE-2026-6382 is a critical command injection vulnerability in Unknown Advanced File Manager, published on 6 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The FileOrganizer  WordPress plugin before 1.1.9, Advanced File Manager  WordPress plugin before 5.4.12, File Manager Pro  WordPress plugin before 2.1.1, File Manager WordPress plugin before 8.0.4 do not properly escape a parameter before passing it to a shell command when processing image operations, allowing authenticated users to perform OS Command Injection. This requires the server to have the ImageMagick convert CLI available without either the PHP imagick or GD extensions.

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


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

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

## Is CVE-2026-6382 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6382 is a critical command injection vulnerability in Unknown Advanced File Manager, published on 6 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6382 in the wild and no public exploit code.

Affected product: Unknown Advanced File Manager. 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-6382/ (Markdown: https://insights.sbomify.com/CVE-2026-6382/index.md)
```

## Sources

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

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