CVE-2006-4904
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 · uneditedDynamic variable evaluation vulnerability in cmpi.php in Qualiteam X-Cart 4.1.3 and earlier allows remote attackers to overwrite arbitrary program variables and execute arbitrary PHP code, as demonstrated by PHP remote file inclusion via the xcart_dir 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 confidenceRemote file inclusion vulnerability in X-Cart's cmpi.php allows attackers to control the xcart_dir parameter and execute arbitrary PHP code through dynamic variable evaluation. This enables complete remote code execution on the affected server.
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.1.3CVSS 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.
-
Locate the cmpi.php file in your X-Cart installationSearch your web root directories for a file named cmpi.php that is part of an X-Cart installation. Common paths include /var/www/html/xcart/ or similar web-accessible directories.Affected if The cmpi.php file exists in your X-Cart web directory, indicating the vulnerable component is present.
-
Determine your installed X-Cart versionCheck the version.php or version.txt file in your X-Cart root directory, or look for a version identifier in the admin panel under system information or about section.Affected if The installed version is X-Cart 4.1.3 or any earlier version (4.1.3, 4.1.2, 4.1.1, 4.1.0, etc.).
-
Inspect cmpi.php for the vulnerable dynamic variable evaluationOpen cmpi.php in a text editor and search for patterns that use the xcart_dir parameter with dynamic variable evaluation techniques such as $$xcart_dir, extract(), or variable variables like ${$xcart_dir}.Affected if The file contains code that evaluates the xcart_dir parameter as a variable variable or uses it in dynamic code execution contexts.
-
Check if user-controlled xcart_dir parameter reaches the dynamic evaluationExamine cmpi.php to see if the xcart_dir parameter is taken directly from user input (GET, POST, or COOKIE) without validation, and passed to the vulnerable dynamic evaluation code.Affected if The xcart_dir parameter is used directly from request input without sanitization and flows into the dynamic variable evaluation code.
Your environment is affected if you have X-Cart version 4.1.3 or earlier with cmpi.php present and the vulnerable code pattern that evaluates the xcart_dir parameter as a dynamic variable.
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 X-Cart 4.1.4 or later, or apply a patch to sanitize/validate the xcart_dir parameter and disable dynamic variable evaluation in cmpi.php.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-4904 — 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-4904 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