CVE-2001-0854
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 · uneditedPHP-Nuke 5.2 allows remote attackers to copy and delete arbitrary files by calling case.filemanager.php with admin.php as an argument, which sets the $PHP_SELF variable and makes it appear that case.filemanager.php is being called by admin.php instead of the user.
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 confidencePHP-Nuke 5.2 contains a flaw in case.filemanager.php where the $PHP_SELF variable can be spoofed by passing admin.php as an argument, causing the application to misinterpret the request source. This allows unauthenticated remote attackers to perform arbitrary file copy and delete operations on the host system.
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= 5.2CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 if PHP-Nuke is installedLook for PHP-Nuke typical files such as index.php containing 'PHP-Nuke' or 'phpnuke' in the source code, or check for the presence of a /html/ or /modules/ directory structure common to PHP-Nuke installations.Affected if PHP-Nuke is present on the server.
-
Determine the PHP-Nuke versionCheck the main index.php file, config.php, or a version.php file within the PHP-Nuke installation for a version number. Compare against the affected range: version 5.2.Affected if The installed version is exactly 5.2.
-
Locate the filemanager moduleSearch for the file 'case.filemanager.php' within the PHP-Nuke directory structure, typically found under /modules/FileManager/ or similar paths within the PHP-Nuke installation.Affected if The file case.filemanager.php exists in the PHP-Nuke installation.
-
Check if the filemanager is accessibleAttempt to access the filemanager module via HTTP request to determine if it is enabled and reachable. Look for admin.php or similar entry points that could be used to trigger the vulnerable code path.Affected if The filemanager module is accessible without authentication.
A system is affected if PHP-Nuke version 5.2 is installed and the case.filemanager.php file is present and accessible, allowing unauthenticated file operations.
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 dataUpgrade from PHP-Nuke 5.2 to a supported version, or if upgrade is not feasible, implement strict authentication checks and input validation on all file operations within the filemanager module.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.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-2001-0854 — 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-2001-0854 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