Skip to main content

FileOrganizer CVE-2026-11962

| EUVDEUVD-2026-41821 HIGH
2026-07-06 WPScan GHSA-mfx2-4vh3-fj3j
8.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain file-manager-capable account
  2. Delivery
    Access FileOrganizer file operation
  3. Exploit
    Upload PHP file bypassing type check
  4. Execution
    Request uploaded file via HTTP
  5. Impact
    Execute arbitrary code as web server

Vulnerability Assessment

Exploitation Conditions

Exploitation requires an authenticated WordPress account that has been granted file-manager access within FileOrganizer (CVSS PR:L confirms low-privilege authentication is needed, so this is not exploitable by anonymous visitors). The premium add-on materially widens exposure by allowing file-manager access to be extended to sub-administrator roles, so environments running the premium add-on with delegated roles face the broadest attacker pool. The specific vulnerable surface is the plugin's file-management operations OTHER than the primary upload (which CVE-2024-7985 already fixed), where file-type validation is absent - the attacker must route the malicious PHP file through one of those operations. Limiting factors: an attacker must first obtain a file-manager-capable account, no exploitation is possible without that grant, and sites that keep file-manager capability restricted to trusted admins and do not enable the sub-administrator extension are far less exposed.

Impact

This is a genuine priority. The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H describes a network-reachable, low-complexity attack needing only low privileges and no user interaction, with high impact to confidentiality, integrity, and availability - consistent with plugin-to-RCE on WordPress. Publicly available exploit code exists, raising near-term risk, though this should not be conflated with active exploitation: it is not listed in CISA KEV, so it counts as no confirmed in-the-wild use at time of analysis. No EPSS score was provided in the input, and no SSVC decision data was supplied, so automatable/technical-impact classifications cannot be quoted here. The main limiting factor is the PR:L requirement - an attacker must already hold a file-manager-capable account (or a sub-administrator role if the premium add-on is installed), which narrows exposure on well-governed sites but is common on multi-user or membership WordPress installs.

Exploit ScenarioDerived

An attacker who holds (or phishes/registers into) a low-privileged WordPress account with file-manager access uses the plugin's unvalidated file-management operation to write a PHP web shell into the site directory, then requests that file over HTTP to run arbitrary code as the web-server user. Because publicly available exploit code exists and the CVSS vector is AV:N/AC:L/UI:N, the attack is straightforward once the required file-manager privilege is obtained and needs no victim interaction.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 06, 2026

Authenticated remote code execution in the FileOrganizer WordPress plugin before 1.2.0 lets users granted file-manager access upload arbitrary PHP files because several file-management operations skip file-type validation. Publicly available exploit code exists, and the flaw is an incomplete fix of CVE-2024-7985, which only hardened the upload operation while leaving other file-management endpoints unvalidated. With CVSS 3.1 base 8.8 (PR:L) and a working PoC, any low-privileged account with file-manager rights - extendable to sub-administrator roles via the premium add-on - can achieve full site compromise.

RemediationAI

Vendor-released patch: upgrade the FileOrganizer plugin to version 1.2.0 or later, which adds the file-type validation missing from the additional file-management operations left unfixed by CVE-2024-7985; confirm the premium add-on is updated in step with the core plugin. Until the update is applied, restrict which accounts hold file-manager capability and remove the add-on grant that extends file-manager access to sub-administrator roles, so only fully trusted administrators retain access; if the file manager is not essential, deactivate the plugin entirely (side effect: staff lose in-dashboard file management). As a defense-in-place measure, deny PHP execution in WordPress upload/content directories via web-server configuration (side effect: may break plugins that legitimately execute files from those paths) and monitor the webroot for newly written .php files. Refer to the WPScan advisory at https://wpscan.com/vulnerability/88390679-80c5-439f-89d1-2f46aff8cfdb/ for details.

Affected VersionsENISA

FileOrganizer 0 <1.2.0

Affected Packages

euvd fileorganizer fix: 1.2.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

FileOrganizer is a WordPress file-management plugin that exposes web-based file operations (upload, copy, rename, move, extract) to users granted file-manager capability. The root cause is a missing/incomplete file-type (extension/MIME) validation on file-management operations other than the primary upload path - an unrestricted file upload weakness (CWE-434 class; NVD lists CWE as N/A). Because WordPress executes any .php file placed under the webroot when requested, writing a PHP payload through an unvalidated operation yields code execution in the web server context. CPE coverage is limited to cpe:2.3:a:unknown:fileorganizer:*:*:*:*:*:*:*:*, reflecting an incomplete NVD CPE record with vendor listed as 'unknown'. Notably, CVE-2024-7985 added validation only to the upload operation, so this CVE addresses the residual bypasses through the plugin's other file-handling endpoints.

Know when Fileorganizer gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable operation with no user interaction, but a granted file-manager account is required (PR:L); arbitrary PHP upload yields full code execution, so C/I/A all High.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Jul 06, 2026 - 13:22 NVD
8.8 (HIGH)
Patch available
Jul 06, 2026 - 09:01 EUVD
CVE Published
Jul 06, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 06, 2026 - 06:00 cve.org
HIGH 8.8

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

FileOrganizer, a widely-used WordPress plugin, contains an authenticated remote code execution vulnerability (CVE-2026-11962, CVSS 8.8) that allows any low-privileged user with file-manager access to upload malicious PHP files and achieve complete site takeover. Publicly available exploit code exists. This affects all organizations running FileOrganizer versions before 1.2.0 and represents a direct path to full WordPress compromise for sites that grant file-management capabilities to contributors or editors.

Business Impact: High
Compensating Controls

Apply vendor patch: upgrade FileOrganizer to version 1.2.0 or later. Interim: restrict file-manager role assignment to administrators only and disable PHP execution in user-upload directories via .htaccess or server configuration.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Medium
WordPress file-manager plugin, common but not on every site
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy