CVE-2007-1096
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 · uneditedCross-site scripting (XSS) vulnerability in ps_cart.php in VirtueMart before 20070116 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. NOTE: this issue might overlap CVE-2007-0376.
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 · moderate confidenceCross-site scripting (XSS) vulnerability in the ps_cart.php file of the VirtueMart e-commerce component allows remote attackers to inject arbitrary JavaScript or HTML through user-supplied input that is not properly sanitized before being rendered in the browser.
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.8CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify installed VirtueMart versionLocate the version file in your VirtueMart installation, typically found in the main directory (e.g., version.php or in the administrator/components/com_virtuemart/virtuemart_version.php). Open the file and read the version number defined within it.Affected if The installed version is 1.0.8 or lower, or if the version cannot be determined and the installation predates January 2007.
-
Verify ps_cart.php file existsCheck for the presence of the file ps_cart.php in the main VirtueMart directory (commonly /administrator/components/com_virtuemart/ or the root if installed as a standalone component).Affected if The file ps_cart.php exists in the VirtueMart installation directory.
-
Inspect ps_cart.php for vulnerable input handlingOpen ps_cart.php in a text editor or use grep to search the file contents. Look for code that handles user-supplied input (particularly from $_REQUEST, $_GET, or $_POST variables) and outputs it directly to HTML without visible sanitization functions such as htmlspecialchars(), htmlentities(), or dedicated XSS filtering.Affected if The file contains code that outputs user input directly to HTML without proper encoding or sanitization, specifically in contexts where product information, cart data, or user parameters are displayed.
-
Check if site processes cart-related user inputTest the storefront by interacting with the cart functionality (adding items, updating quantities, navigating to cart page). Observe whether parameters submitted to ps_cart.php (such as product_id, cart_id, or other query string or form parameters) are reflected in the page output.Affected if User-supplied values submitted through cart functionality are reflected in the browser output without encoding, indicating the XSS vulnerability is present and exploitable.
You are affected if VirtueMart version 1.0.8 or lower is installed, the ps_cart.php file exists, and user input from cart operations is reflected in the page output without proper HTML encoding.
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 dataImplement proper input validation and output encoding/escaping for all user-supplied data in ps_cart.php, or upgrade VirtueMart to version 20070116 or later which contains the security fix.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1096 — 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-2007-1096 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