CVE-2006-4526
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/viewCat.inc.php in CubeCart 3.0.12 and earlier, when register_globals is enabled, allows remote attackers to execute arbitrary SQL commands via the searchArray[] 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 3.0.12 and earlier allows remote attackers to execute arbitrary SQL commands via the searchArray[] parameter in includes/content/viewCat.inc.php, specifically when PHP's register_globals is enabled.
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<= 3.0.12CVSS 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 installed CubeCart versionLocate the CubeCart version file or check the admin dashboard for the version number. Common locations include a version.php file in the root or includes/ directory, or the admin panel's system info page.Affected if The installed version is 3.0.12 or any earlier version (3.0.x series)
-
Verify PHP register_globals settingCheck the PHP configuration file (php.ini) for 'register_globals = On', or create a PHP info page (<?php phpinfo(); ?>) and search for the register_globals value.Affected if register_globals is set to On or On is implied (not explicitly Off in PHP 5.3 or earlier)
-
Confirm vulnerable script existsCheck for the presence of includes/content/viewCat.inc.php in the CubeCart installation directory.Affected if The file exists and is accessible via the web server
-
Determine if application is internet-facingReview network configuration to confirm whether the CubeCart installation is accessible from external networks or the internet.Affected if The web server hosting CubeCart is exposed to untrusted networks
You are affected if your CubeCart version is 3.0.12 or earlier AND PHP's register_globals setting is enabled, allowing the SQL injection via the searchArray[] parameter in viewCat.inc.php.
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 dataDisable PHP's register_globals setting (or upgrade from PHP 5.3 and earlier where it was available), and apply vendor patches or upgrade to a newer CubeCart version that properly sanitizes the searchArray[] parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4526 — 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-4526 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