CVE-2006-3139
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 · uneditedMultiple SQL injection vulnerabilities in war.php in Virtual War (VWar) 1.5.0 R14 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) s, (2) showgame, (3) sortorder, and (4) sortby parameters.
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 confidenceMultiple SQL injection vulnerabilities exist in war.php of Virtual War (VWar) 1.5.0 R14 and earlier. The s, showgame, sortorder, and sortby GET parameters are not properly sanitized before being used in SQL queries, allowing remote unauthenticated attackers to inject arbitrary SQL commands.
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.0_r14= 1.5.0_r1= 1.5.0_r2= 1.5.0_r3= 1.5.0_r4= 1.5.0_r5= 1.5.0_r6= 1.5.0_r7= 1.5.0_r8= 1.5.0_r9= 1.5.0_r10= 1.5.0_r11CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Locate the VWar installationSearch the web server document root for the 'war.php' file or the 'vwar' directory commonly associated with Virtual War installations.Affected if The file war.php exists in the web root or a subdirectory.
-
Identify the VWar versionOpen the admin panel or check version files included with VWar (typically found in an 'admin' or 'includes' directory) to determine the exact version number.Affected if The installed version is 1.5.0 R14 or any earlier release (R1 through R13).
-
Examine war.php for vulnerable parameter usageOpen war.php in a text editor and search for usage of the GET parameters: $s, $showgame, $sortorder, $sortby. Check if these variables are directly inserted into SQL queries without sanitization functions such as mysql_real_escape_string, addslashes, or parameterized queries.Affected if The parameters are used directly in SQL queries without any escaping or prepared statement implementation.
-
Verify the application handles these parametersReview the war.php source code to confirm that the parameters s, showgame, sortorder, and sortby are processed and passed to database queries.Affected if The application accepts these GET parameters and uses them in dynamic SQL construction.
A system is affected if VWar version 1.5.0 R14 or earlier is installed, war.php is accessible, and the s, showgame, sortorder, or sortby GET parameters are used in SQL queries without proper sanitization or prepared statements.
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 dataReplace dynamic SQL query construction with parameterized queries/prepared statements for all four affected parameters, or implement proper input validation and escaping. Apply vendor security patches if available.
- 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-2006-3139 — 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-2006-3139 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