CVE-2006-2158
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 · uneditedDynamic variable evaluation vulnerability in index.php in Stadtaus Guestbook Script 1.7 and earlier, when register_globals is enabled, allows remote attackers to modify arbitrary program variables via parameters, which are evaluated as PHP variable variables, as demonstrated by performing PHP remote file inclusion using the include_files array 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 confidenceDynamic variable evaluation vulnerability in Stadtaus Guestbook Script 1.7 and earlier allows remote attackers to modify arbitrary PHP program variables via URL parameters when register_globals is enabled. The attacker exploits PHP variable variables ($$) to inject values that can trigger remote file inclusion through the include_files array parameter.
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.7CVSS 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
- None
AV:N/AC:L/Au:N/C:P/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.
-
Confirm Stadtaus Guestbook Script is installedSearch the web root directory for guestbook-related PHP files such as guestbook.php, index.php, or a 'stadtaus' or 'guestbook' directory containing PHP scripts.Affected if The Stadtaus Guestbook Script files are present on the server.
-
Identify the installed version of the guestbook scriptOpen the main PHP script file (typically index.php or guestbook.php) and search for a version string or variable such as '$version', '$script_version', or similar. Check any included config files for version information.Affected if The discovered version is 1.7 or any version lower than 1.7.
-
Verify the register_globals PHP settingCreate a temporary PHP file containing '<?php phpinfo(); ?>' and access it via a browser, then search for the 'register_globals' line in the output. Alternatively, check the php.ini file for 'register_globals = On'.Affected if register_globals is set to On or any value other than Off.
-
Locate the include_files parameter usage in the codeSearch the guestbook PHP source files for 'include_files' or variable variable patterns '$$' to confirm the vulnerable code path exists in the installed version.Affected if The code contains an 'include_files' array parameter and uses variable variable syntax ($$).
The environment is affected if Stadtaus Guestbook Script version 1.7 or earlier is installed AND register_globals is enabled in PHP, allowing the variable injection vulnerability to be exploited.
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 a patched version of the guestbook script; also implement input validation to prevent variable injection.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2158 — 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-2158 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