Quick answers
- Is CVE-2026-11962 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11962 being exploited in the wild.
- How severe is CVE-2026-11962?
- Informational severity, with a CVSS score of 8.8, published 6 July 2026.
- Which products and versions are affected?
- FileOrganizer before 1.2.0.
- Is there a fix for CVE-2026-11962?
- A patch was published on 2026-07-06: Fixed in version 1.2.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11962 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-11962?
- Check whether you run FileOrganizer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The FileOrganizer plugin for WordPress is vulnerable to authenticated arbitrary file upload due to insufficient file type validation across multiple elFinder-based file management operations. While a previous fix (CVE-2024-7985) addressed the primary upload function, other operations remained unprotected. An attacker with file-manager permissions—which can be granted to sub-administrator roles via the plugin's premium add-on—can exploit this to upload PHP files to the server. Successful exploitation results in Remote Code Execution (RCE) in the context of the web server. The issue is resolved in version 1.2.0.
Affected products
- Unknown FileOrganizer before 1.2.0
Timeline
- 2026-06-15: disclosed
- 2026-07-06: advisory: NVD publication date
- 2026-07-06: patched: Fixed in version 1.2.0