CVE-2011-3813
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 · uneditedVirtual War (aka VWar) 1.5.0r15 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 includes/language/dutch.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 · high confidenceVWar 1.5.0r15 contains an information disclosure vulnerability where direct HTTP requests to certain PHP files (such as includes/language/dutch.inc.php) cause the application to reveal the full installation path in error messages. This path disclosure can aid attackers in reconnaissance and targeting further attacks.
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.5.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.
-
Confirm Vwar 1.5.0 installationIdentify Vwar Virtual War installation by locating vwar.php or index.php with Vwar branding, or check for vwar directory in web rootAffected if Vwar version 1.5.0 is installed on the server
-
Check for vulnerable PHP filesLook for the file includes/language/dutch.inc.php (and similar language files in includes/language/) within the Vwar installation directoryAffected if The file includes/language/dutch.inc.php exists in the web-accessible path
-
Test for path disclosureSend a direct HTTP GET request to includes/language/dutch.inc.php using a tool like curl or browser - request the PHP file directly without proper parametersAffected if The HTTP response contains the full server file system path (such as /var/www/html/vwar/includes/language/dutch.inc.php) in an error message
-
Verify PHP error display is enabledCheck php.ini for display_errors = On, or inspect PHP configuration via phpinfo() or a test scriptAffected if PHP error display is enabled (display_errors=On) and error messages are visible to web requests
A user is affected if Vwar 1.5.0 is installed, vulnerable PHP files exist in web-accessible paths, and direct HTTP requests to those files expose the full installation 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 dataDisable PHP error display and configure custom error handlers to prevent path disclosure. Alternatively, add .htaccess restrictions or move sensitive include files outside the web root.
- 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-3813 — 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-3813 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