CVE-2004-0240
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 · uneditedDirectory traversal vulnerability in X-Cart 3.4.3 allows remote attackers to view arbitrary files via a .. (dot dot) in the shop_closed_file argument to auth.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 confidenceDirectory traversal vulnerability in X-Cart 3.4.3 allows remote attackers to read arbitrary files on the server by injecting '..' sequences into the shop_closed_file parameter passed to auth.php, enabling unauthorized access to sensitive system files.
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.2.0= 3.2.1= 3.3.0= 3.3.2= 3.4.0= 3.4.3= 3.4.11CVSS 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.
-
Identify if X-Cart is installedLook for the auth.php file in the web root or check for X-Cart-specific directories and files such as 'auth.php', 'config.php', or the 'skin' directory with X-Cart branding.Affected if The presence of X-Cart files in the web directory confirms X-Cart is installed.
-
Determine the X-Cart versionOpen the auth.php file and look for a version identifier in the comments or header, or check for a VERSION file in the X-Cart root directory.Affected if The installed version matches one of the affected versions: 3.2.0, 3.2.1, 3.3.0, 3.3.2, 3.4.0, 3.4.3, or 3.4.11.
-
Verify the shop_closed_file parameter is processedExamine the auth.php file to confirm it processes the 'shop_closed_file' parameter, typically by checking if this parameter is referenced in the code and used in file inclusion operations.Affected if The auth.php script reads and processes the shop_closed_file parameter without sanitizing path traversal sequences.
-
Confirm lack of input sanitizationReview the auth.php code around the shop_closed_file handling to verify there is no validation that strips or rejects '..' sequences or validates the path is within an allowed directory.Affected if The code does not validate or sanitize the shop_closed_file parameter, allowing directory traversal characters to pass through unchecked.
A defender is affected if X-Cart is installed with a version matching 3.2.0 through 3.4.11 and the shop_closed_file parameter in auth.php is processed without sanitizing directory traversal sequences.
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 version of X-Cart that addresses this vulnerability, or implement input validation to sanitize the shop_closed_file parameter and reject path traversal sequences.
- 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-2004-0240 — 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-0240 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