CVE-2006-2535
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 · uneditedindex.php in Destiney Links Script 2.1.2 allows remote attackers to obtain the installation path via an invalid show parameter referencing a non-existent file, which reveals the path in the resulting error message. NOTE: this issue might be resultant from a more serious issue such as directory traversal.
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 confidenceThe index.php script in Destiney Links Script 2.1.2 is vulnerable to information disclosure via path exposure. When an invalid 'show' parameter referencing a non-existent file is provided, the application returns an error message containing the full server filesystem path to the installation directory, which could aid attackers in reconnaissance or exploiting other vulnerabilities.
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= 2.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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 Destiney Links Script installationLocate index.php in the web root and verify it is the Destiney Links Script by checking the file header or page content for 'Destiney Links Script' brandingAffected if The script is present in the web directory
-
Verify installed version is 2.1.2Open index.php or any version file within the installation directory and look for a version identifier, typically displayed as '2.1.2' or in a version constantAffected if The version displayed is exactly 2.1.2
-
Test vulnerable 'show' parameterSend a request to index.php with an invalid 'show' parameter value referencing a non-existent file, for example: index.php?show=nonexistent_file.phpAffected if The response contains a PHP error message that reveals the full server filesystem path to the installation directory
-
Check PHP display_errors settingCreate a PHPinfo page or check the server configuration for the display_errors directive. In a local PHP environment, create a file with '<?php phpinfo(); ?>' and access itAffected if display_errors is set to On in php.ini, .htaccess, or at runtime
You are affected if Destiney Links Script version 2.1.2 is installed and the application reveals the server's filesystem path when an invalid 'show' parameter is provided, typically due to PHP's display_errors being enabled.
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 PHP's display_errors setting in production environments and implement custom error handling that presents generic error messages to users without exposing filesystem paths.
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2535 — 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-2535 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