CVE-2007-5735
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 · uneditedeFileMan 7.1.0.87-88 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain unspecified user information via a direct request for cgi-bin/efileman/efileman_config.pm.
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 confidenceeFileMan 7.1.0.87-88 stores a configuration file (efileman_config.pm) containing sensitive user information in a publicly accessible web directory (cgi-bin/efileman/). Remote attackers can directly request this file via HTTP to obtain the stored sensitive information without authentication.
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.1.0.87_88CVSS 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.
-
Confirm eFileMan is installedCheck the system for the presence of eFileMan software, typically in the web server's cgi-bin directory. Look for directories named 'efileman' or files such as 'efileman_config.pm' on the web server.Affected if eFileMan version 7.1.0.87 or 7.1.0.88 is installed on the server
-
Locate the configuration fileSearch for the file 'efileman_config.pm' within the web server's document root, particularly under cgi-bin/efileman/ or similar web-accessible paths.Affected if The file efileman_config.pm exists in a web-accessible directory
-
Test HTTP access to the config fileUsing a web browser or curl command, attempt to directly request the URL: http://<server>/cgi-bin/efileman/efileman_config.pm (adjust path based on actual installation). Check if the file is served and returns contents.Affected if The server returns the file contents via HTTP without requiring authentication
-
Verify sensitive data exposureIf the file is accessible, examine its contents for sensitive information such as usernames, passwords, database credentials, or other configuration data that should not be publicly accessible.Affected if The accessible config file contains plaintext sensitive information such as credentials or user data
A server is affected if eFileMan 7.1.0.87 or 7.1.0.88 is installed and the efileman_config.pm file in cgi-bin/efileman/ is directly accessible via HTTP, exposing sensitive configuration data.
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 dataRelocate the configuration file containing sensitive data outside the web root directory, or implement proper web server access controls (e.g., .htaccess deny rules) to prevent direct HTTP access to the cgi-bin/efileman/ directory.
- 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-5735 — 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-5735 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