CVE-2006-1433
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 · uneditedAnnuaire (Directory) 1.0 allows remote attackers to obtain sensitive information via a direct request to include/lang-en.php, which reveals the full installation path.
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 confidenceAnnuaire 1.0 contains an information disclosure vulnerability where directly requesting include/lang-en.php reveals the full server installation path. This path disclosure can aid attackers in crafting further attacks by revealing filesystem structure.
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.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
- 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.
-
Verify Annuaire 1.0 installationLocate the Annuaire Directory installation by searching for characteristic files such as index.php, annuaire.php, or the include/lang-en.php file within the web server document root.Affected if Annuaire Directory version 1.0 is installed on the server
-
Confirm vulnerable file existsCheck if the file include/lang-en.php exists within the Annuaire installation directory.Affected if The file include/lang-en.php exists in the web-accessible directory
-
Test direct HTTP access to vulnerable fileSend an HTTP GET request directly to http://[target]/include/lang-en.php (or the equivalent path within the Annuaire installation) using a web browser, curl, or similar tool.Affected if The server responds with a page that displays the full filesystem path (such as /var/www/html/annuaire/include/lang-en.php or C:\inetpub\wwwroot\annuaire\include\lang-en.php)
-
Inspect response for path disclosureExamine the HTTP response body for any visible server filesystem paths. The vulnerability manifests as the full server path being displayed in the page output.Affected if The response contains absolute server paths that reveal the document root or installation directory structure
The environment is affected if Annuaire Directory version 1.0 is installed and directly requesting include/lang-en.php via HTTP reveals the server's full filesystem path.
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 dataRestrict direct access to include files by adding access control checks at the beginning of PHP files, moving include files outside the web root, or configuring the web server to deny direct access to the include directory.
- 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-1433 — 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-1433 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