CVE-2009-4060
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 includes/content/viewProd.inc.php in CubeCart before 4.3.7 remote attackers to execute arbitrary SQL commands via the productId parameter.
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 CubeCart's product display functionality (includes/content/viewProd.inc.php) allows remote attackers to inject arbitrary SQL commands through the productId parameter. The vulnerability affects versions prior to 4.3.7 and could enable attackers to read, modify, or delete database contents including user credentials and sensitive business data.
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<= 4.3.6= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.0.7= 3.0.8= 3.0.9= 3.0.10CVSS 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 CubeCart installation versionLocate the version file or check the admin dashboard for the installed CubeCart version. Common locations include a version.php file in the root or documentation, or view the admin panel's system information page.Affected if The installed version is 4.3.6 or lower, or is any version in the 3.0.0 through 3.0.10 range.
-
Verify vulnerable file presenceCheck if the file includes/content/viewProd.inc.php exists in the CubeCart web root directory.Affected if The file exists and the application version is in the affected ranges listed above.
-
Check productId parameter handlingExamine the viewProd.inc.php file and verify whether the productId parameter is used in direct SQL queries without proper sanitization or parameterized queries.Affected if The code contains unsanitized SQL queries using the productId parameter.
-
Review input validation implementationLook for input validation functions applied to the productId parameter before database queries in the application code.Affected if No input validation or parameterized queries are implemented for the productId parameter.
A system is affected if it runs CubeCart version 4.3.6 or lower, or any version from 3.0.0 to 3.0.10, and contains the vulnerable viewProd.inc.php file that handles the productId parameter without proper SQL injection protection.
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 CubeCart version 4.3.7 or later which contains the patched code. If immediate upgrade is not feasible, implement proper input validation and parameterized queries for the productId parameter as a compensating control.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-4060 — 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-2009-4060 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