CVE-2006-6945
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 · uneditedSQL injection vulnerability in Virtuemart 1.0.7 allows remote attackers to execute arbitrary SQL commands via unspecified vectors, probably related to (1) Itemid, (2) product_id, and category_id parameters as handled in virtuemart_parser.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 confidenceSQL injection vulnerability in Virtuemart 1.0.7 allows remote attackers to execute arbitrary SQL commands via Itemid, product_id, and category_id parameters in virtuemart_parser.php. Unsanitized user input is passed directly to SQL queries, enabling injection 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.0.7CVSS 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 virtuemart_parser.php fileSearch the web server document root for the file virtuemart_parser.php. Common paths include /administrator/components/com_virtuemart/virtuemart_parser.php or /components/com_virtuemart/virtuemart_parser.php.Affected if The file exists in the installation and is accessible via the web root.
-
Verify Virtuemart version is 1.0.7Check the version declaration in the Virtuemart installation. Look for a version.php file or check the database for the version string. Common locations include /administrator/components/com_virtuemart/virtuemart.php or the database configuration table.Affected if The installed version is exactly 1.0.7.
-
Inspect vulnerable parameter usage in virtuemart_parser.phpOpen virtuemart_parser.php and search for direct usage of the parameters 'Itemid', 'product_id', and 'category_id' from $_GET, $_POST, or $_REQUEST arrays being inserted into SQL queries without escaping or parameterized binding.Affected if Any of these parameters are used directly in SQL queries without sanitization functions such as mysql_real_escape_string, addslashes, or prepared statements.
-
Confirm the file handles user input for these parametersExamine the code around lines where these parameters are processed. Verify whether $_REQUEST['Itemid'], $_REQUEST['product_id'], or $_REQUEST['category_id'] are concatenated into SQL statements.Affected if User-supplied values for Itemid, product_id, or category_id are concatenated into SQL queries without validation or escaping.
If Virtuemart 1.0.7 is installed and virtuemart_parser.php contains direct use of Itemid, product_id, or category_id parameters in SQL queries without sanitization, the environment is affected by CVE-2006-6945.
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 dataUpgrade Virtuemart to a patched version or apply input validation/parameterized queries to the affected parameters in virtuemart_parser.php. If upgrading is not feasible, implement immediate input filtering as a temporary workaround.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-6945 — 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-6945 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