CVE-2006-2096
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 · uneditedplug.php in Land Down Under (LDU) 802 and earlier allows remote attackers to obtain sensitive information via an invalid (1) month or (2) year parameter, which reveals the path in an error message.
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 plug.php script in Land Down Under (LDU) 802 and earlier fails to properly validate the month and year parameters. When invalid values are provided for these parameters, the script returns verbose error messages that disclose the server's filesystem path. This path disclosure vulnerability aids attackers in reconnaissance efforts by revealing absolute paths that can be used to craft further attacks.
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<= 802= 601= 602= 700.01= 700.02= 700.03= 700.04= 700.05= 701= 800= 801CVSS 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.
-
Locate the plug.php scriptSearch the web root directory for the file named plug.php, which is part of the Land Down Under (LDU) application.Affected if The file plug.php exists in the web-accessible directory.
-
Identify the LDU versionCheck the version information in the LDU installation, typically found in a configuration file, readme, or by accessing the admin panel. Compare the version number against the affected list: 601, 602, 700.01, 700.02, 700.03, 700.04, 700.05, 701, 800, 801, or 802.Affected if The installed version is any of the versions listed in the affected products range.
-
Test the month parameter for path disclosureSend an HTTP request to plug.php with an invalid month value, such as month=99 or month=abc, and examine the error response for disclosure of absolute filesystem paths.Affected if The error response contains an absolute server path (for example, /home/user/public_html/).
-
Test the year parameter for path disclosureSend an HTTP request to plug.php with an invalid year value, such as year=9999 or year=invalid, and examine the error response for disclosure of absolute filesystem paths.Affected if The error response contains an absolute server path (for example, /home/user/public_html/).
You are affected if the LDU version is 802 or earlier and invalid month or year parameters passed to plug.php expose absolute filesystem paths in error messages.
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 dataImplement strict input validation on the month and year parameters (month should be 1-12, year should be a valid format) and configure custom error handling to display generic error messages instead of exposing full filesystem paths in production environments.
- 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-2096 — 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-2096 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