CVE-2011-3788
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 · uneditedPhpSecInfo 0.2.1 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by Test/Test_Suhosin.php and certain other files.
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 confidencePhpSecInfo 0.2.1 contains a test directory with PHP files that, when accessed directly via HTTP, produce error messages revealing the full server installation path. This path disclosure occurs in files like Test/Test_Suhosin.php and similar test files.
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.1CVSS 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 PhpSecInfo 0.2.1 installationCheck if the PhpSecInfo library is installed on your server. Look for the main phpsecinfo.php file or the PhpSecInfo class in your web root or application directory.Affected if PhpSecInfo version 0.2.1 is present on the server
-
Confirm Test directory existsLocate the Test/ subdirectory within the PhpSecInfo installation. Look for Test/Test_Suhosin.php or similar test PHP files in the same location.Affected if The Test/ directory with PHP test files exists in the PhpSecInfo installation
-
Test HTTP access to Test directoryAttempt to access a test file directly via HTTP, for example: http://yourserver/path/to/phpsecinfo/Test/Test_Suhosin.phpAffected if The HTTP request returns an error page or output instead of a 403/404 denial
-
Check for path disclosure in error outputExamine the response from the direct HTTP access to any Test/*.php file. Look for the full server filesystem path in error messages, such as in PHP error messages, stack traces, or warning outputs.Affected if The error output contains the complete server filesystem path (e.g., /var/www/html/... or C:\inetpub\...)
You are affected if PhpSecInfo 0.2.1 is installed with the Test/ directory accessible via HTTP and direct access to test PHP files reveals the server's full filesystem path 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 dataRemove the entire Test/ directory from production deployments, or restrict access to it via web server configuration (e.g., deny all HTTP requests to the Test/ path).
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3788 — 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-2011-3788 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