CVE-2011-3815
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 · uneditedWeBid 1.0.0 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 js/calendar.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 confidenceWeBid 1.0.0 contains multiple PHP files that can be requested directly without proper initialization, causing PHP to output error messages that reveal the server's installation file path. The js/calendar.php file and other similar files are vulnerable to this path disclosure.
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.0.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.
-
Identify if WeBid 1.0.0 is installedCheck for the presence of WeBid by looking for its main files (such as index.php, admin.php, or configuration files) in the web root directory. Check version.php or any version file if available.Affected if The installed version is Webidsupport Webid version 1.0.0
-
Locate vulnerable PHP filesSearch for the file js/calendar.php in the web document root. Also look for other PHP files in subdirectories (js/, includes/, etc.) that might lack proper initialization includes.Affected if The file js/calendar.php exists in the installation
-
Check if direct access reveals path informationMake an HTTP request directly to js/calendar.php (e.g., GET /js/calendar.php) without going through normal application initialization. Inspect the HTTP response for PHP error messages or warnings that contain absolute file system paths.Affected if The response contains error messages displaying full server file paths (e.g., /var/www/html/webid/...) or warning messages about missing includes/requires
-
Verify PHP error display is enabledCheck the PHP configuration file (php.ini) for the setting 'display_errors = On' or inspect a PHP info page to confirm whether error display is enabled on the server.Affected if display_errors is set to On in PHP configuration, allowing error messages to be displayed to the client
A user is affected if WeBid version 1.0.0 is installed, the js/calendar.php file exists, direct access to it produces PHP error messages showing server paths, and PHP error display is enabled on the server.
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 PHP error display in production environments and/or add proper initialization/include guards to prevent direct access to vulnerable PHP files, ensuring they cannot be executed outside the application's normal flow.
- 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-2011-3815 — 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-3815 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