CVE-2007-0230
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 · uneditedPHP remote file inclusion vulnerability in install.php in CS-Cart 1.3.3 allows remote attackers to execute arbitrary PHP code via a URL in the install_dir parameter. NOTE: CVE and third parties dispute this vulnerability because install_dir is defined before use
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 · moderate confidencePHP remote file inclusion vulnerability in install.php in CS-Cart 1.3.3 allows remote attackers to execute arbitrary PHP code via a URL in the install_dir parameter. However, the CVE description notes that CVE and third parties dispute this vulnerability because install_dir is defined before use, raising questions about actual exploitability.
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= 1.3.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.
-
Identify CS-Cart installation and versionLocate the CS-Cart installation directory and check the version file (typically includes/config.php or a version.php file). Look for version markers indicating 1.3.3.Affected if The installed version is exactly 1.3.3
-
Locate install.php fileSearch for install.php in the web root or application directory. Common paths include /install.php or /admin/install.php.Affected if install.php exists in the application directory
-
Examine install_dir parameter handling in install.phpOpen install.php and locate where the install_dir parameter is used. Check if it is assigned a default value before any user input is processed, and trace whether user-supplied values can override the defined variable.Affected if install_dir is defined with a static value before user input is processed, suggesting the parameter may not be controllable
-
Check for user input acceptance on install_dirSearch the install.php code for $_GET, $_POST, or $_REQUEST references to install_dir. Verify if the parameter is used directly in include/require statements without proper validation.Affected if install_dir is directly used in include/require statements and accepts user input without validation
-
Determine if application is in production useVerify whether install.php has been removed or disabled. Check if the application is accessible in a production environment where install scripts should be absent.Affected if install.php is present and accessible in a production environment
A user is affected only if CS-Cart version 1.3.3 is installed, install.php exists and is accessible, and the install_dir parameter can be controlled by an attacker to inject arbitrary code.
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 dataIf the vulnerability is confirmed, remediate by ensuring proper input validation on the install_dir parameter or by removing/disabling install.php in production environments. If disputed and not reproducible, document the finding as non-exploitable and ensure install scripts are removed from production as a security best practice.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0230 — 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-2007-0230 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