CVE-2006-2122
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 index.php in CoolMenus allows remote attackers to execute arbitrary code via a URL in the page parameter. NOTE: the original report for this issue is probably erroneous, since CoolMenus does not appear to be written in PHP.
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 · low confidenceDescribes a PHP remote file inclusion vulnerability in CoolMenus index.php via the 'page' parameter, allowing arbitrary code execution. However, the CVE description itself notes the report is probably erroneous since CoolMenus does not appear to be written in PHP, creating significant uncertainty about whether this vulnerability is valid.
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.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Verify if CoolMenus is a PHP applicationInspect your deployed files for CoolMenus. Check if it contains PHP files (.php extension) or if it is a different technology (such as a DHTML/JavaScript menu system). Look for an index.php file within the CoolMenus directory structure.Affected if CoolMenus is NOT a PHP-based application - if it uses only JavaScript, HTML, or other non-PHP technologies, this CVE does not apply and should be treated as disputed.
-
Locate index.php and inspect for 'page' parameter usageIf CoolMenus is a PHP application, find the index.php file in the CoolMenus directory. Open the file and search for usage of the 'page' parameter. Check if it is used in include(), require(), include_once(), or require_once() functions without proper sanitization.Affected if The 'page' parameter is directly used in an include/require statement without input validation - for example: include($page); or include($_GET['page']); This would indicate a remote file inclusion vulnerability.
-
Check the installed CoolMenus versionLook for a version identifier within the CoolMenus files (often in a README, VERSION file, or within the main script comments). Compare your installed version to the affected range: Coolmenus Coolmenus version 4.0Affected if The installed version is Coolmenus Coolmenus version 4.0 AND the conditions from step 2 are met (PHP application with vulnerable code pattern).
You are affected only if CoolMenus in your environment is a PHP application, version 4.0, AND the index.php file contains unsafe inclusion of the 'page' parameter. If CoolMenus is not PHP-based, treat this CVE as invalid and disputed.
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 dataVerify whether CoolMenus is actually a PHP application; if so, audit index.php for unsafe inclusion of the page parameter and implement input validation or disable allow_url_include. If not PHP, treat as invalid and close as disputed.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2122 — 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-2122 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