CVE-2006-5900
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 · uneditedCross-site scripting (XSS) vulnerability in the incubator/tests/Zend/Http/_files/testRedirections.php sample code in Zend Framework Preview 0.2.0 allows remote attackers to inject arbitrary web script or HTML via arbitrary parameters.
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 confidenceCross-site scripting (XSS) vulnerability in Zend Framework Preview 0.2.0's test file (incubator/tests/Zend/Http/_files/testRedirections.php). The vulnerability allows remote attackers to inject arbitrary web script or HTML via unsanitized parameters in sample test code that was inadvertently shipped in the release.
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= 0.2.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.
-
Identify Zend Framework versionCheck the version file or library headers in your Zend Framework installation directory. Common locations include a VERSION file or version metadata in the main library files.Affected if The installed version is Zend Framework Preview 0.2.0 exactly.
-
Locate the vulnerable test fileSearch for the file at incubator/tests/Zend/Http/_files/testRedirections.php within your Zend Framework installation directory.Affected if The file exists in your Zend Framework installation.
-
Verify file accessibilityAttempt to access the file via HTTP/HTTPS through your web server using the path to incubator/tests/Zend/Http/_files/testRedirections.phpAffected if The test file is web-accessible and returns the file contents or executes the PHP code.
-
Check parameter handlingSubmit a test request with a crafted parameter (e.g., ?param=<script>alert(1)</script>) to the test file URL and observe if the script tag is reflected in the response without encoding.Affected if The test file reflects unsanitized user input in its output, confirming the XSS vulnerability is present and exploitable.
You are affected if you have Zend Framework Preview 0.2.0 installed AND the test file at incubator/tests/Zend/Http/_files/testRedirections.php exists and is web-accessible.
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 dataRemove or disable the vulnerable test/sample files from production deployments. If retention is required, implement proper input validation and output encoding for all user-supplied parameters before reflecting them in HTTP responses.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5900 — 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-5900 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