CVE-2006-5441
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 Web Blogger 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 · moderate confidenceRemote file inclusion (RFI) vulnerability in adminfoot.php of Comdev Web Blogger 4.1 allows arbitrary PHP code execution via the path[docroot] parameter. The vulnerability requires register_globals to be enabled, an older PHP configuration setting that was deprecated in PHP 5.3 and removed in PHP 5.4.
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.
-
Confirm Comdev Web Blogger versionLocate the application and identify its exact version number (typically found in a version file, about page, or HTTP headers). Compare to the affected version: 4.1Affected if The installed version is Comdev Web Blogger 4.1
-
Locate adminfoot.phpSearch the web root directory for the file adminfoot.php (typically in the admin or includes subdirectory of the Comdev Web Blogger installation)Affected if adminfoot.php exists in the application directory structure
-
Verify register_globals is enabledCheck the PHP configuration (php.ini) for the setting 'register_globals = On'. You can also check this at runtime using phpinfo() or by checking $_SERVER['PHP_SELF'] access and observing if arbitrary parameters become automatically defined as variablesAffected if register_globals is set to On in the PHP configuration
-
Inspect adminfoot.php for vulnerable parameter usageExamine the source code of adminfoot.php and locate where $path[docroot] is used in include or require statements without sanitization. Look for patterns like 'include($path[docroot] . "/...")' or 'require($path[docroot] . "...")' where the parameter is not validated before useAffected if adminfoot.php uses the path[docroot] parameter in include/require statements without input validation
A system is affected if it runs Comdev Web Blogger 4.1 with adminfoot.php present and register_globals enabled, allowing the path[docroot] parameter to inject arbitrary PHP code via includes.
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 (or upgrade to PHP 5.4+ where it no longer exists) and patch adminfoot.php to validate/sanitize the path[docroot] parameter before use in include/require statements.
- 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-5441 — 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-5441 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