CVE-2005-1033
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 · uneditedCubeCart 2.0.6 allows remote attackers to obtain sensitive information via an invalid (1) language parameter to index.php, (2) PHPSESSID parameter to index.php, (3) product parameter to tellafriend.php, (4) add parameter to view_cart.php, or (5) product parameter to view_product.php, which reveals the path in a PHP error message.
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 confidenceCubeCart 2.0.6 exposes absolute server file paths through verbose PHP error messages when invalid parameters (language, PHPSESSID, product, add) are supplied to index.php, tellafriend.php, view_cart.php, and view_product.php - this is a path disclosure information leak vulnerability.
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= 2.0.6CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Confirm CubeCart version 2.0.6 is installedInspect the CubeCart source files (such as includes/global.php, version.php, or the admin dashboard) to identify the installed version number. Compare it against the affected version = 2.0.6.Affected if The installed version is exactly 2.0.6.
-
Verify PHP display_errors is enabledCheck your php.ini file for 'display_errors = On' or run phpinfo() and look for the display_errors directive. You can also create a PHP info file to inspect this setting.Affected if display_errors is set to On (On is the vulnerable configuration).
-
Test path disclosure on index.phpSend an HTTP request to index.php with an invalid parameter, such as ?language=invalid or ?product=invalid, and examine the response for absolute file paths in error messages.Affected if The response contains absolute server file paths (for example, /home/user/public_html/).
-
Test path disclosure on view_cart.phpSend an HTTP request to view_cart.php with an invalid parameter, such as ?PHPSESSID=invalid or ?add=invalid, and examine the response for absolute file paths in error messages.Affected if The response displays absolute server paths in PHP error output.
-
Test path disclosure on tellafriend.php and view_product.phpSend HTTP requests to tellafriend.php and view_product.php with malformed parameters (such as ?product=invalid or arbitrary invalid values) and inspect the responses for absolute file path disclosure.Affected if Either script returns absolute file paths in verbose PHP error messages.
You are affected if CubeCart 2.0.6 is installed AND PHP display_errors is enabled, causing absolute file paths to appear in error messages when invalid parameters are submitted to the affected scripts.
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 error display (display_errors=Off) and set error_reporting to 0 in production php.ini, and implement custom error handling to prevent sensitive path information from being returned to users.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1033 — 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-2005-1033 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