dbcve.org
Comdev Csv ImporterApplication · Comdev

CVE-2006-5101

HIGH · 7.5 CVSS v2.0 Published 2006-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
PHP remote file inclusion vulnerability in include.php in Comdev CSV Importer 3.1 and possibly 4.1, as used in (1) Comdev Contact Form 3.1, (2) Comdev Customer Helpdesk 3.1, (3) Comdev Events Calendar 3.1, (4) Comdev FAQ Support 3.1, (5) Comdev Guestbook 3.1, (6) Comdev Links Directory 3.1, (7) Comdev News Publisher 3.1, (8) Comdev Newsletter 3.1, (9) Comdev Photo Gallery 3.1, (10) Comdev Vote Caster 3.1, (11) Comdev Web Blogger 3.1, and (12) Comdev eCommerce 3.1, allows remote attackers to execute arbitrary PHP code via a URL in the path[docroot] parameter. NOTE: it has been reported that 4.1 versions might also be affected.

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 confidence

This is a remote file inclusion (RFI) vulnerability in the include.php file of Comdev CSV Importer versions 3.1 and possibly 4.1. The vulnerability stems from unsanitized user input being used in the path[docroot] parameter, allowing an attacker to supply a remote URL that the PHP interpreter will execute. This affects at least 12 different Comdev products that incorporate this CSV Importer component.

MitigationThe most effective remediation is to upgrade to a patched version of the CSV Importer if available, or alternatively, implement strict input validation on the path[docroot] parameter to ensure only expected values are accepted, and disable allow_url_include in PHP configuration.

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
Comdev Csv ImporterApplication
Affected:= 3.1= 4.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the CSV Importer include.php file
    Search the web root directories for the file 'include.php' within any 'csv' or 'importer' directories, or within Comdev product installations. Common paths may include /csv_importer/include.php or similar patterns.
    Affected if The file include.php exists in the web-accessible directory structure.
  2. Identify the Comdev product and CSV Importer version
    Inspect the source code of include.php for version comments, or check for version files in the same directory. Look for version numbers 3.1 or 4.1 specifically.
    Affected if The installed CSV Importer version is 3.1 or 4.1 (or an unpatched version in that range).
  3. Verify the path[docroot] parameter handling
    Examine the include.php code to see if the $_GET['path[docroot]'] or similar parameter is used in include/require statements without sanitization. Search for 'path[docroot]' in the code.
    Affected if The parameter path[docroot] is used in include/require operations without input validation or sanitization.
  4. Confirm the include.php is web-accessible
    Check web server configuration to confirm the include.php file is accessible via HTTP/HTTPS from the web. Attempt a direct request to the suspected path.
    Affected if The vulnerable include.php is reachable over the network via the web server.

A system is affected if it runs Comdev CSV Importer version 3.1 or 4.1 with the include.php file accessible via the web and the path[docroot] parameter processed without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The most effective remediation is to upgrade to a patched version of the CSV Importer if available, or alternatively, implement strict input validation on the path[docroot] parameter to ensure only expected values are accepted, and disable allow_url_include in PHP configuration.

Fix this in Comdev Csv Importer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-5101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-5101 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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