CVE-2006-5439
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 remote file inclusion vulnerability in adminfoot.php in Comdev Misc Tools 4.1, when register_globals is enabled, allows remote attackers to execute arbitrary PHP code via a URL in the path[docroot] parameter. NOTE: the provenance of this information is unknown; the details are obtained from third party information.
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 confidenceRemote file inclusion vulnerability in adminfoot.php of Comdev Misc Tools 4.1 allows arbitrary PHP code execution through the path[docroot] parameter when register_globals is enabled. Attackers can specify a remote URL containing malicious PHP code that gets included and executed by the vulnerable script.
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= 4.1CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Locate Comdev Misc Tools installationSearch for adminfoot.php file in your web server's document root and any subdirectories, or check your web application files for the Comdev Misc Tools packageAffected if adminfoot.php from Comdev Misc Tools 4.1 is present on the server
-
Verify the installed versionCheck the product version string in the source code, README, or any version file within the Comdev Misc Tools installation directoryAffected if The installed version is exactly 4.1
-
Check if register_globals is enabledCreate a PHP script containing '<?php echo ini_get("register_globals"); ?>' and access it via your web server, or check your php.ini configuration file for the register_globals settingAffected if register_globals is set to On or 1 in php.ini or the script outputs On/1
-
Confirm the vulnerable parameter is accessibleInspect the adminfoot.php source code to verify it uses the path[docroot] parameter without proper sanitization and that register_globals is required for exploitationAffected if adminfoot.php contains code that uses the path[docroot] variable and requires register_globals to be enabled for the parameter to be populated from user input
Your environment is affected only if Comdev Misc Tools version 4.1 is installed, the adminfoot.php file exists, and register_globals is enabled in PHP configuration.
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 dataDisable register_globals in php.ini (register_globals = Off) and upgrade to a patched version of Comdev Misc Tools if available, or remove/restrict access to the vulnerable adminfoot.php file.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5439 — 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-2006-5439 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