dbcve.org
VulnerabilityAwaiting classification

CVE-2026-6382

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Multiple WordPress file management plugins (FileOrganizer, Advanced File Manager, File Manager Pro, and File Manager) fail to properly escape parameters before passing them to shell commands during image processing operations, allowing authenticated users to inject and execute arbitrary OS commands. The vulnerability is specifically triggered when the server has ImageMagick's convert CLI available but lacks PHP's imagick or GD extensions.

MitigationUpdate all affected plugins to their latest versions (FileOrganizer 1.1.9+, Advanced File Manager 5.4.12+, File Manager Pro 2.1.1+, File Manager 8.0.4+) and verify that shell command execution in image operations is properly sanitized.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed WordPress file manager plugins
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for FileOrganizer, Advanced File Manager, File Manager Pro, or File Manager. Alternatively, inspect the wp-content/plugins/ directory for folders starting with 'fileorganizer', 'advanced-file-manager', 'file-manager-pro', or 'file-manager'.
    Affected if Any of these four plugins are installed on the WordPress site
  2. Determine installed plugin version
    For each identified plugin, open its main PHP file (usually in the plugin root directory) and locate the version comment in the plugin header, or check the readme.txt file for the 'Stable tag' entry. Compare this version against the known patched versions: FileOrganizer 1.1.9, Advanced File Manager 5.4.12, File Manager Pro 2.1.1, File Manager 8.0.4.
    Affected if The installed version is older than the corresponding patched version for that plugin
  3. Check if ImageMagick convert CLI is available
    Run the command 'which convert' or 'command -v convert' in the server terminal. Alternatively, create a PHP script with '<?php echo shell_exec('which convert'); ?>' and access it via a web browser, or check the server's PATH environment for ImageMagick binaries.
    Affected if The convert command returns a valid file path, indicating ImageMagick is installed and accessible
  4. Check if PHP imagick extension is missing
    Run 'php -m' from the command line to list loaded PHP modules, or create a phpinfo page '<?php phpinfo(); ?>' and search for 'imagick' in the loaded modules section. Alternatively, check the output of '<?php echo extension_loaded('imagick') ? 'loaded' : 'not loaded'; ?>'
    Affected if The imagick extension does not appear in the list of loaded PHP modules
  5. Check if PHP GD extension is missing
    Run 'php -m' from the command line and search for 'gd' in the output, or access a phpinfo page and look for the GD section. Alternatively, check with '<?php echo extension_loaded('gd') ? 'loaded' : 'not loaded'; ?>'
    Affected if The GD extension does not appear in the list of loaded PHP modules

A user is affected if they have any of the four plugins installed with a version below the patched release AND the server has ImageMagick's convert CLI available AND both PHP imagick and GD extensions are absent, allowing the vulnerable image processing code path to be triggered.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update all affected plugins to their latest versions (FileOrganizer 1.1.9+, Advanced File Manager 5.4.12+, File Manager Pro 2.1.1+, File Manager 8.0.4+) and verify that shell command execution in image operations is properly sanitized.

Recommended fix High confidence

Upgrade to: FileOrganizer 1.1.9, Advanced File Manager 5.4.12, File Manager Pro 2.1.1, File Manager 8.0.4

  1. 1. Backup your WordPress site and database before performing any updates.
  2. 2. Ensure your server has proper authentication controls - the vulnerability requires authenticated access.
  3. 3. Navigate to WordPress Admin Dashboard > Plugins.
  4. 4. For each affected plugin (FileOrganizer, Advanced File Manager, File Manager Pro, File Manager), update to the specified fixed version.
  5. 5. If automatic updates are not available, manually upload the updated plugin files via WordPress plugin upload or FTP.
  6. 6. Verify the updated plugin version matches the fixed release.
  7. 7. Test file management functionality to ensure the plugin works correctly after update.
  8. 8. Consider implementing additional security measures such as restricting file manager access to trusted users only.
Caveat Minor risk: WordPress plugin updates may temporarily affect site functionality; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6382 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data