CVE-2004-1579
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 · uneditedindex.php in CubeCart 2.0.1 allows remote attackers to gain sensitive information via an HTTP request with an invalid cat_id parameter, which reveals the full 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 confidenceAn information disclosure vulnerability in CubeCart 2.0.1's index.php allows remote attackers to discover the server's full filesystem path through crafted HTTP requests with an invalid cat_id parameter, which triggers verbose PHP error messages revealing the absolute path.
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.1CVSS 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 is 2.0.1Locate the version file or check the admin panel for the installed CubeCart version. Common locations include a version.php file or the footer in the admin dashboard.Affected if The installed version is exactly 2.0.1 (other versions are not affected by this specific CVE)
-
Verify index.php exists and is accessibleCheck if the web application file index.php exists in the web root directory and is accessible via HTTP.Affected if The index.php file exists and responds to HTTP requests
-
Test for path disclosure with invalid cat_idSend an HTTP GET request to index.php with an invalid cat_id parameter, for example: index.php?cat_id=999999999 or index.php?cat_id=invalidAffected if The response contains PHP error messages or warnings that reveal the absolute server filesystem path (e.g., /var/www/html/cubecart/)
-
Check PHP error display configurationInspect the PHP configuration (php.ini) or the CubeCart configuration files to determine if display_errors is set to On.Affected if PHP display_errors is enabled, which allows verbose error messages to be returned to the requester
A user is affected if they are running CubeCart version 2.0.1 AND the application exposes PHP error messages that reveal the server's absolute filesystem path when an invalid cat_id parameter is supplied.
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 error handling in index.php to catch invalid cat_id parameters and display generic error messages instead of PHP error traces that reveal filesystem paths.
- 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-2004-1579 — 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-2004-1579 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