CVE-2011-3806
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 · uneditedTCExam 11.1.015 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 public/code/tce_page_footer.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 confidenceTCExam 11.1.015 contains multiple PHP files that, when accessed directly, trigger PHP errors that disclose the server's installation path. This information disclosure occurs in files such as public/code/tce_page_footer.php and can expose sensitive filesystem location data to remote attackers.
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= 11.1.015CVSS 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 TCExam installation versionLocate the version file or check version-related code in your TCExam installation directory. Common locations include a version.php file, README file, or the main index/header file that displays version information.Affected if The installed version is exactly 11.1.015 (not a range, this CVE affects only this specific version)
-
Confirm vulnerable file existsCheck if the file public/code/tce_page_footer.php exists in your TCExam installation directory.Affected if The file exists in the expected location within your TCExam installation
-
Test direct access to vulnerable PHP fileAttempt to access http://your-server/tcexam/public/code/tce_page_footer.php directly via a web browser or curl command. If the application is configured to allow direct access, the file will execute and may display PHP errors.Affected if Direct HTTP access to the file is permitted and returns output containing error messages or reveals filesystem paths
-
Check if error display is enabledInspect your PHP configuration (php.ini) or check the runtime configuration using phpinfo() to determine if display_errors is set to On.Affected if display_errors is enabled (On), which allows PHP error messages including installation paths to be visible to visitors
-
Verify include file access controlsReview your web server configuration and TCExam .htaccess or access control settings to determine if direct access to PHP include files in the public/code/ directory is restricted.Affected if No access controls exist to block direct access to include files, allowing external users to trigger error conditions
You are affected if TCExam version 11.1.015 is installed AND direct access to PHP files like public/code/tce_page_footer.php is possible AND PHP display_errors is enabled, allowing path disclosure through 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 dataConfigure PHP to disable error display (display_errors=Off) or implement proper access controls to prevent direct access to include files, ensuring error messages do not reveal installation 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-2011-3806 — 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-3806 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