CVE-2007-4655
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 · uneditedMultiple directory traversal vulnerabilities in CGI RESCUE Shopping Basket Professional 7.51 and earlier allow remote attackers to list arbitrary directories, and possibly read arbitrary files, via directory traversal sequences in unspecified parameters to (1) list.cgi or (2) list2.cgi.
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 confidenceDirectory traversal vulnerability in CGI RESCUE Shopping Basket Professional (list.cgi and list2.cgi) allows remote attackers to use '..' sequences in unspecified parameters to traverse the filesystem, list arbitrary directories, and potentially read arbitrary files on the 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<= 7.51CVSS 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.
-
Locate Shopping Basket Professional installationSearch web server directories for the CGI RESCUE Shopping Basket Professional script directories. Look for directories containing 'shopping', 'basket', or 'cart' in the path, typically under the web document root (e.g., /var/www/html/, /www/, cgi-bin/).Affected if The product is installed on the server in any web-accessible location.
-
Identify the installed versionCheck the version number in the main script file (usually shopping basket.cgi or similar), or in a version/README file within the Shopping Basket Professional directory. Look for a version string or $VERSION variable.Affected if The installed version is 7.51 or any version lower than 7.51.
-
Verify presence of vulnerable scriptsConfirm that list.cgi and/or list2.cgi exist in the Shopping Basket Professional installation directory. These are the specific scripts with the directory traversal vulnerability.Affected if list.cgi or list2.cgi are present in the installation.
-
Check if CGI execution is enabledReview the web server configuration (httpd.conf, .htaccess) to determine if CGI scripts are permitted to execute in the directory where list.cgi or list2.cgi are located. Look for 'Options +ExecCGI' or 'ScriptAlias' directives.Affected if CGI execution is enabled for the directory containing the vulnerable scripts, allowing them to be executed via HTTP requests.
A user is affected if they have CGI RESCUE Shopping Basket Professional version 7.51 or lower installed with list.cgi or list2.cgi present and CGI execution enabled on their web server.
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 dataImplement strict input validation to reject directory traversal sequences ('..') in all parameters, or upgrade to a patched version if available. Restrict filesystem permissions and web server access to minimize exposure.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4655 — 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-4655 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