CVE-2011-3786
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 · uneditedPHProjekt 6.0.5 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 Setup/Controllers/IndexController.php.
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 confidencePHProjekt 6.0.5 contains an information disclosure vulnerability where direct HTTP requests to certain PHP files (such as Setup/Controllers/IndexController.php) cause the application to reveal the full server installation path in error messages. This path disclosure can aid attackers in reconnaissance and enumerating the system's file 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= 6.0.5CVSS 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.
-
Identify PHProjekt versionLocate the version file or check the application admin interface for the installed PHProjekt version number. Compare against the affected version 6.0.5.Affected if The installed version is exactly 6.0.5
-
Check for direct script access vulnerabilitySend a direct HTTP GET request to Setup/Controllers/IndexController.php via curl or browser (e.g., http://yourserver/path/to/phprojekt/Setup/Controllers/IndexController.php).Affected if The PHP file is accessible via direct HTTP request and can be executed outside the normal application flow.
-
Inspect error messages for path disclosureExamine the HTTP response from the direct request for any error messages, warnings, or stack traces. Look for absolute file system paths in the output.Affected if The error output contains the full server installation path (e.g., /var/www/html/phprojekt or C:\inetpub\wwwroot\phprojekt)
You are affected if you are running PHProjekt 6.0.5 AND direct HTTP requests to Setup/Controllers/IndexController.php reveal the full server 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 dataRestrict direct access to PHP files that should not be executed directly by implementing access control checks at the top of vulnerable scripts or using web server configuration (e.g., .htaccess rules) to block unauthorized requests. Alternatively, disable detailed PHP error messages in production environments.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3786 — 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-3786 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