dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11962

HIGH · 8.8 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 →
94/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.2.0 does not validate the file type on several of its file-management operations, allowing authenticated users who have been granted file-manager access — which its premium add-on can extend to sub-administrator roles — to upload arbitrary PHP files and achieve remote code execution. This is an incomplete fix of CVE-2024-7985, which only added file-type validation to the upload operation.

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 · high confidence

The FileOrganizer WordPress plugin before version 1.2.0 fails to validate file types on multiple file-management operations beyond just the upload function. While CVE-2024-7985 added file-type validation to the upload operation, other file-management operations remain unprotected, allowing authenticated users with file-manager access to upload arbitrary PHP files and achieve remote code execution.

MitigationUpdate to FileOrganizer version 1.2.0 or later, which adds file-type validation to all file-management operations. Additionally, restrict file-manager access to only highly trusted users and consider disabling the premium add-on if sub-administrator role access extension is not needed.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Locate the FileOrganizer plugin version
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and find FileOrganizer. The version number is displayed below the plugin name. Alternatively, inspect the plugin main file header in wp-content/plugins/file-organizer/
    Affected if The installed version is lower than 1.2.0 (e.g., 1.1.x, 1.0.x, or any version before 1.2.0)
  2. Confirm the plugin is active
    In Plugins > Installed Plugins, verify that FileOrganizer shows as Active. Inactive plugins do not expose the vulnerability.
    Affected if FileOrganizer is active and the version is below 1.2.0
  3. Verify file-manager access is enabled
    Check if the FileOrganizer file-manager functionality is accessible. This typically requires a user role with file-manager permissions (such as administrator or a custom role with file-manager access granted through the plugin settings).
    Affected if Authenticated users with file-manager role permissions can access file-management operations and the plugin version is below 1.2.0
  4. Identify users with file-manager role permissions
    Review user accounts and their assigned roles. FileOrganizer may create or modify roles to grant file-manager capabilities. Check Users > All Users and examine role assignments, or inspect the file-organizer roles/capabilities configuration.
    Affected if Any user account has a role that includes file-manager access and the plugin version is below 1.2.0

The environment is affected if FileOrganizer plugin version is below 1.2.0, the plugin is active, and any authenticated user has access to file-management operations.

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 to FileOrganizer version 1.2.0 or later, which adds file-type validation to all file-management operations. Additionally, restrict file-manager access to only highly trusted users and consider disabling the premium add-on if sub-administrator role access extension is not needed.

Recommended fix High confidence

FileOrganizer plugin version 1.2.0

  1. Update the FileOrganizer WordPress plugin to version 1.2.0 or later through the WordPress admin dashboard under Plugins > Installed Plugins
  2. Alternatively, update via WP-CLI: wp plugin update file-organizer
  3. Verify the update was successfully applied by checking the plugin version in the Plugins list
  4. Ensure file-type validation is functioning on all file-management operations after the update
  5. Review user permissions to ensure only trusted users have file-manager access

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11962 — 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-11962 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