dbcve.org
Virtual WarApplication · Vwar

CVE-2006-2091

MEDIUM · 5.0 CVSS v2.0 Published 2006-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
admin.php in Virtual War (VWar) 1.5 and versions before 1.2 allows remote attackers to obtain sensitive information via an invalid vwar_root parameter, which reveals the path in an error message.

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 confidence

admin.php in Virtual War (VWar) 1.5 and earlier versions contains an information disclosure vulnerability where an invalid vwar_root parameter causes the application to reveal the full server file system path in an error message. This path information can aid attackers in reconnaissance for subsequent attacks.

MitigationImplement proper input validation and error handling in admin.php to either validate the vwar_root parameter or display generic error messages that do not expose file system paths. Consider upgrading to a patched version if available.

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
Virtual WarApplication
Affected:= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1.0= 1.1.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate VWar installation
    Search the web server document root for the VWar application files, particularly looking for admin.php or any version indicator files such as version.php, info.php, or a CHANGELOG file that may contain the version number
    Affected if VWar is installed on the server and the version is 1.5 or earlier (versions 1.0.0 through 1.1.1 are explicitly listed as affected)
  2. Verify admin.php exists
    Confirm that the admin.php file exists within the VWar web directory and is accessible via HTTP/HTTPS
    Affected if The admin.php file is present and web-accessible
  3. Check the installed version
    Open any version information file within the VWar installation or access the main VWar page to view the displayed version number, then compare against the affected range (1.0.0 through 1.1.1, or any version 1.5 or earlier)
    Affected if The installed version matches 1.0.0 through 1.1.1 or is otherwise 1.5 or earlier
  4. Test for path disclosure
    Send an HTTP request to admin.php with an invalid or malformed value for the vwar_root parameter (for example: admin.php?vwar_root=invalid_path), then examine any error messages returned in the response
    Affected if The error message displays the full server file system path (such as /var/www/html/vwar/ or similar absolute path)
  5. Review error output
    Inspect the HTML or source of the response from the previous test for any directory paths, absolute file paths, or server configuration details that should not be exposed to end users
    Affected if Any server filesystem paths, absolute paths to VWar files, or internal directory structures are visible in error output

The environment is affected if VWar version 1.5 or earlier (specifically 1.0.0 through 1.1.1) is installed, admin.php is accessible, and sending an invalid vwar_root parameter reveals the full server file system path in an error message.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and error handling in admin.php to either validate the vwar_root parameter or display generic error messages that do not expose file system paths. Consider upgrading to a patched version if available.

Fix this in Virtual War Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-2091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-2091 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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