CVE-2006-4214
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 Zen Cart 1.3.0.2 and earlier allow remote attackers to execute arbitrary SQL commands via (1) GPC data to the ipn_get_stored_session function in ipn_main_handler.php, which can be leveraged to modify elements of $_SESSION; and allow remote authenticated users to execute arbitrary SQL commands via (2) a session id within a cookie to whos_online_session_recreate, (3) the quantity field to the add_cart function, (4) an id[] parameter when adding an item to a shopping cart, or (5) a redemption code when checking out (dc_redeem_code parameter to includes/modules/order_total/ot_coupon.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 confidenceMultiple SQL injection vulnerabilities in Zen Cart 1.3.0.2 allow remote attackers to execute arbitrary SQL commands. The most severe vector (ipn_main_handler.php) is unauthenticated and allows modification of $_SESSION via GPC data. Additional authenticated vectors exist in session handling, cart operations (quantity field, id[] parameter), and coupon redemption (dc_redeem_code).
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.3.0.2CVSS 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.
-
Identify Zen Cart installationLook for characteristic Zen Cart files such as /includes/application_top.php, /admin/index.php, or the presence of 'zenid' session parameters in cookies or URLsAffected if Zen Cart files are present and the application is running
-
Determine Zen Cart versionCheck the version.php file typically located in the /includes/ directory, or look for version strings in the main index.php or a README fileAffected if The installed version is 1.3.0.2 or any earlier version (1.3.0, 1.2.x, 1.1.x, etc.)
-
Verify ipn_main_handler.php is presentCheck if the file /ipn_main_handler.php exists in the web root. This is the most severe unauthenticated SQL injection vectorAffected if The file exists and is accessible via the web server
-
Check if session handling allows GPC injectionReview the session configuration in /includes/configure.php and /includes/application_top.php to see if PHP's register_globals or auto_globals_jit settings permit $_SESSION manipulation via GET/POST parametersAffected if register_globals is enabled or user-supplied input can directly populate $_SESSION variables
-
Verify shopping cart module is enabledConfirm the shopping cart functionality is active by checking for the presence of shopping_cart.php or the 'id[]' parameter handling in the applicationAffected if The shopping cart feature is enabled and accessible without additional authentication
-
Check for coupon/reward moduleLook for the presence of discount_coupon code or dc_redeem_code handling in the admin or catalog sections, typically in files related to discount couponsAffected if The coupon redemption feature is installed and accessible
A user is affected if they are running any Zen Cart version 1.3.0.2 or earlier and have the ipn_main_handler.php file accessible or have the shopping cart or coupon features exposed.
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 to a patched Zen Cart version or apply vendor-provided security patches that implement parameterized queries and input validation for all user-supplied parameters in the identified vulnerable functions.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4214 — 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-4214 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