CVE-2024-4300
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 · uneditedE-WEBInformationCo. FS-EZViewer(Web) exposes sensitive information in the service. A remote attacker can obtain the database configuration file path through the webpage source code without login. Accessing this path allows attacker to obtain the database credential with the highest privilege and database host IP address. With this information, attackers can connect to the database and perform actions such as adding, modifying, or deleting database contents.
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 confidenceE-WEBInformationCo. FS-EZViewer(Web) contains an information disclosure vulnerability where database configuration files containing credentials and host IP addresses are exposed through the web application's source code. Attackers can access these files without authentication, obtaining high-privilege database credentials that enable full database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 FS-EZViewer installationCheck your web server document root for files or directories containing 'FS-EZViewer', 'ezviewer', or E-WEBInformationCo signatures. Search for the application's main entry point (often index.php or similar).Affected if FS-EZViewer software is present on the server
-
Locate database configuration filesWithin the application directory, look for common configuration file names such as config.php, db.php, database.php, connection.php, or .env files. Also search for XML or JSON configuration files that may contain database settings.Affected if Database configuration files exist within the application web root
-
Test unauthenticated access to configuration filesAttempt to access identified configuration files directly via HTTP/HTTPS requests (e.g., GET /config.php, GET /include/config.php). Use a web browser or curl to verify if the files are directly downloadable or viewable without authentication.Affected if Configuration files are accessible without authentication (HTTP returns 200 instead of 403/404)
-
Inspect configuration file contents for credentialsIf accessible, examine the configuration files for plain-text database credentials, usernames, passwords, and host IP addresses. Look for patterns such as $dbhost, $dbuser, $password, $connection_string, or similar variables.Affected if Database credentials or host IP addresses are present in web-accessible configuration files
-
Verify web root exposure of sensitive filesReview your web server configuration to confirm whether configuration, include, or data directories are within the web-accessible path. Check for missing .htaccess restrictions or similar access controls on directories containing sensitive files.Affected if Sensitive configuration directories are served by the web server without access restrictions
A user is affected if FS-EZViewer is installed and its database configuration files containing credentials or host IPs are accessible via direct web requests without authentication.
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 dataRemove or secure database configuration files from web-accessible paths, implement proper access controls on sensitive configuration files, rotate all exposed database credentials immediately, and conduct a security review to identify similar exposures in the application.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4300 — 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-2024-4300 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