CVE-2025-46001
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 · uneditedAn 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.
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 confidenceThe is_allowed_file_type() function in Filemanager v2.3.0 fails to properly validate file types during upload, allowing attackers to bypass restrictions and upload malicious PHP files that can be executed for arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.8, <= 1.1>= 1.5.0, <= 2.0.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Filemanager versionLocate the version information in the Filemanager installation (typically in a version file, README, or header comments of main PHP files). Common locations include 'version.php', 'config.php', or the main 'filemanager.php' entry point.Affected if The installed version falls within 0.8 to 1.1 inclusive, or 1.5.0 to 2.0.0 inclusive.
-
Confirm file upload functionality is enabledCheck the Filemanager configuration for the upload feature setting. Look for parameters like 'upload' or 'enable_upload' in the configuration file.Affected if File uploads are permitted in the Filemanager configuration.
-
Locate the is_allowed_file_type() functionSearch the Filemanager source code for the is_allowed_file_type() function definition. This is typically found in PHP files handling file operations or validation logic.Affected if The function exists and is used in the upload processing flow.
-
Examine the file type validation logicInspect the is_allowed_file_type() function implementation to determine if it properly validates MIME types and blocks executable extensions like .php, .phtml, .exe.Affected if The function allows executable file extensions or relies solely on client-provided MIME types without proper server-side validation.
You are affected if your Filemanager version is between 0.8-1.1 or 1.5.0-2.0.0 AND file uploads are enabled AND the is_allowed_file_type() function does not properly block executable file extensions.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataFix the is_allowed_file_type() function to properly validate MIME types and block executable file extensions (e.g., .php, .phtml, .exe) while allowing only safe document types.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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