Skip to main content
VulnerabilityPublished Updated

CVE-2025-46001: Filemanager · An Arbitrary File Upload

Affects FilemanagerSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubsimogeo/Filemanagerpkg:github/simogeo/FilemanagerOther threatsAffected
  • =2.3.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate mitigation should include disabling or restricting file upload functionality in Filemanager v2.3.0 until a patch is available.
  2. Implement strict server-side validation of uploaded files, including checking MIME types, file extensions, and file content signatures to ensure only allowed file types are accepted.
  3. Employ web application firewalls (WAFs) with rules to detect and block attempts to upload PHP or other executable files.
  4. Restrict execution permissions on directories used for file uploads to prevent execution of uploaded scripts.
  5. Monitor logs for suspicious upload attempts and anomalous file executions.
  6. If possible, isolate the Filemanager application in a sandboxed environment or container to limit potential damage.
  7. Regularly update and patch Filemanager once an official fix is released.
  8. Conduct security audits and penetration testing focused on file upload mechanisms.
  9. Educate developers and administrators about secure file upload practices to prevent similar vulnerabilities.

Description

An arbitrary file upload vulnerability in the is_allowed_file_type() function of Filemanager v2.3.0 allows attackers to execute arbitrary code via uploading a crafted PHP file.

References

Community reviews

Loading reviews…