CVE-2005-2786
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 · uneditedDirectory traversal vulnerability in bestmail_edit.cgi in cosmoshop 8.10.78 and earlier allows remote administrators to read arbitrary files via ".." sequences in the file 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 confidenceDirectory traversal vulnerability in bestmail_edit.cgi component of cosmoshop e-commerce software (versions 8.10.78 and earlier). Allows authenticated remote administrators to read arbitrary files on the server by using '..' sequences in the file parameter, bypassing intended path restrictions.
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= 8.10.78CVSS 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.
-
Identify if Cosmoshop is installedSearch the web server for cosmoshop files or directories. Common locations include /cgi-bin/, /cosmoshop/, or the web root. Check for files named bestmail_edit.cgi or any cosmoshop-related scripts.Affected if Cosmoshop software is present on the server.
-
Determine the installed Cosmoshop versionLocate version information in Cosmoshop configuration files, help files, or the main index page. Look for files like version.txt, or check the HTML source of Cosmoshop pages for version strings.Affected if The installed version is 8.10.78 or earlier.
-
Verify bestmail_edit.cgi existsSearch for the bestmail_edit.cgi script in the cgi-bin or cosmoshop directories. This is the specific component containing the vulnerability.Affected if The bestmail_edit.cgi file exists on the server.
-
Confirm administrator access to bestmail_edit.cgiCheck if the bestmail_edit.cgi script is accessible through the web interface and whether administrative authentication is configured. The vulnerability requires authenticated administrator privileges.Affected if Remote administrator authentication is enabled and accessible for the bestmail_edit.cgi component.
-
Test for directory traversal in the file parameterIf authenticated as administrator, submit a request to bestmail_edit.cgi with a file parameter containing '../' sequences (such as ../../../etc/passwd) to see if arbitrary files can be read.Affected if The script allows reading files outside the intended directory using '..' sequences in the file parameter.
A server is affected if Cosmoshop version 8.10.78 or earlier is installed, bestmail_edit.cgi is present, and the directory traversal vulnerability is exploitable through the authenticated administrator interface.
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 cosmoshop to a version newer than 8.10.78. Alternatively, implement strict input validation to reject '..' sequences in the file parameter and enforce proper path bounds checking on all file operations.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2786 — 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-2005-2786 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