CVE-2006-6217
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 formdisp.php in the Mermaid 1.2 module for PHP-Nuke allows remote attackers to execute arbitrary PHP code via a URL in the module_name parameter.
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 confidenceThis is a Remote File Inclusion (RFI) vulnerability in the Mermaid module for PHP-Nuke. The formdisp.php file uses the module_name parameter in an include/require statement without sanitization, allowing attackers to inject arbitrary PHP code by specifying a remote URL.
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= 1.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
- 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 the Mermaid module installationSearch for the 'Mermaid' module directory in your PHP-Nuke installation, typically under modules/Mermaid/ or modules/mermaid/Affected if The Mermaid module directory exists in your PHP-Nuke modules folder
-
Identify the vulnerable fileLook for formdisp.php within the Mermaid module directory (modules/Mermaid/formdisp.php or modules/mermaid/formdisp.php)Affected if The file formdisp.php exists in the Mermaid module directory
-
Check the Mermaid module versionExamine version information in the module directory - look for files like version.php, module.xml, or any README/install file that states the version numberAffected if The installed version is 1.2 or any unpatched version of the Mermaid module
-
Inspect the include/require usage in formdisp.phpOpen formdisp.php and search for lines using $_GET['module_name'] or $module_name in include(), require(), include_once(), or require_once() statements without sanitization functions like basename() or allowlist validationAffected if The code uses the module_name parameter directly in include/require without input validation or uses it in a way that allows remote URLs (no local path enforcement)
-
Verify PHP allows remote file inclusionCheck your PHP configuration file (php.ini) for the allow_url_include setting - if set to On, remote file inclusion attacks can succeedAffected if allow_url_include is enabled in php.ini (this setting is deprecated as of PHP 5.2 but if present and On, the RFI can execute remote code)
You are affected if the Mermaid module version 1.2 (or unpatched) is installed, formdisp.php exists with unsanitized module_name parameter in include/require, and PHP's allow_url_include is enabled or the attacker can control the include path.
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 dataSanitize the module_name parameter before use in include/require statements - implement allowlist validation or basename() checks to prevent path traversal and remote file inclusion.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6217 — 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-6217 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