CVE-2011-3775
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 · uneditedPHPfileNavigator 2.3.3 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 xestion/varios/logs.inc.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 · moderate confidencePHPfileNavigator 2.3.3 contains an information disclosure vulnerability where direct HTTP requests to certain PHP files (such as xestion/varios/logs.inc.php) cause the application to reveal the full installation path in error messages. This occurs because these files are accessible directly rather than being properly included through entry points, and PHP error reporting is enabled.
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.3.3CVSS 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 PHPfileNavigator versionCheck the application's version file or header - typically in an about.php, version info in main index, or readme fileAffected if The installed version is exactly 2.3.3
-
Check if vulnerable file existsLocate the file xestion/varios/logs.inc.php (or similar files in xestion/varios/ directory) in the web rootAffected if The file exists in the web-accessible directory
-
Test direct HTTP access to include fileSend an HTTP request directly to xestion/varios/logs.inc.php (e.g., GET /xestion/varios/logs.inc.php) and observe the responseAffected if The response contains a full server file path in an error message (such as 'Warning: include()' or 'Fatal error' messages showing the absolute path)
-
Check PHP display_errors settingRun 'php -i' or create a PHP info page to check if display_errors is set to On, or check php.ini for the display_errors directiveAffected if display_errors is enabled (On)
A user is affected if they run PHPfileNavigator version 2.3.3, the vulnerable include file is web-accessible, and PHP display_errors is enabled, allowing path disclosure through direct HTTP requests.
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 display_errors in php.ini and ensure all include files are accessed only through proper application entry points rather than direct HTTP requests, or add .htaccess restrictions to deny direct access to include files.
- 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-2011-3775 — 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-3775 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