CVE-2007-0190
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 edit_address.php in edit-x ecommerce allows remote attackers to execute arbitrary PHP code via a URL in the include_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 confidencePHP remote file inclusion (RFI) vulnerability in edit_address.php of the edit-x ecommerce application. The include_dir parameter allows remote attackers to supply an external URL containing malicious PHP code, which the server will include and execute, leading to arbitrary code execution.
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 dataall versionsCVSS 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.
-
Confirm Edit X Ecommerce installationSearch your web server directories for the edit-x or editx ecommerce application files, typically in web root or subdirectories.Affected if The Edit X Ecommerce application is found on the server
-
Locate edit_address.phpFind the file named edit_address.php within the Edit X Ecommerce installation directory.Affected if The file edit_address.php exists in the application
-
Verify include_dir parameter usageExamine edit_address.php source code and look for dynamic include statements that use the include_dir parameter, such as include($_REQUEST['include_dir']) or similar constructions.Affected if The code contains dynamic includes using the include_dir parameter without sanitization
-
Check PHP remote file inclusion settingsReview php.ini or run phpinfo() to check if allow_url_include is enabled (On value).Affected if allow_url_include is set to On, allowing inclusion of remote URLs
-
Check allow_url_fopen settingReview php.ini or run phpinfo() to check if allow_url_fopen is enabled.Affected if allow_url_fopen is set to On, allowing PHP to open remote files
The environment is affected if Edit X Ecommerce is installed, edit_address.php exists with dynamic include_dir parameter usage, and PHP allows remote URL inclusions via allow_url_include or allow_url_fopen.
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 dataSanitize and validate the include_dir parameter using a whitelist of allowed directories, or better yet, remove the dynamic include functionality entirely. Additionally, disable allow_url_include and allow_url_fopen in php.ini as a defense-in-depth measure.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0190 — 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-0190 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