CVE-2019-7305
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 · uneditedInformation Exposure vulnerability in eXtplorer makes the /usr/ and /etc/extplorer/ system directories world-accessible over HTTP. Introduced in the Makefile patch file debian/patches/debian-changes-2.1.0b6+dfsg-1 or debian/patches/adds-a-makefile.patch, this can lead to data leakage, information disclosure and potentially remote code execution on the web server. This issue affects all versions of eXtplorer in Ubuntu and Debian
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 confidenceeXtplorer versions in Ubuntu and Debian contain an information exposure vulnerability where the Makefile patch incorrectly configures web server access, making /usr/ and /etc/extplorer/ system directories world-accessible over HTTP. Attackers can directly request sensitive system files, leading to credential theft, configuration disclosure, and potentially remote code execution.
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<= 2.1.0CVSS 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.
-
Check if eXtplorer is installedOn Debian/Ubuntu systems, run: dpkg -l | grep extplorer or dpkg -L extplorer to list installed files. Check for version with: apt-cache policy extplorerAffected if eXtplorer package is installed and version is 2.1.0 or lower, or if the extplorer package files exist on the system
-
Identify the web server configurationCheck for Apache config: ls -la /etc/apache2/sites-enabled/ or /etc/apache2/sites-available/. For Nginx: ls -la /etc/nginx/sites-enabled/ or /etc/nginx/sites-available/. Look for extplorer-related configuration filesAffected if A web server is configured to serve eXtplorer files and the configuration contains Allow directives for the affected directories
-
Inspect web server access rules for /etc/extplorer/Search for rules allowing access to /etc/extplorer/ in Apache config files (grep -r "etc/extplorer" /etc/apache2/ or /etc/httpd/) or Nginx config files (grep -r "etc/extplorer" /etc/nginx/). Check for 'Require all granted' (Apache) or similar access rulesAffected if Web server configuration contains rules that allow HTTP access to /etc/extplorer/ directory (such as 'Require all granted' or 'allow all' directives)
-
Inspect web server access rules for /usr/Search for rules allowing access to /usr/ in web server configs, particularly in extplorer-specific config files. Look for Apache 'Allow from all' or 'Require all granted' directives targeting the /usr directoryAffected if Web server configuration contains rules that allow HTTP access to /usr/ directory, particularly in eXtplorer-related configs
-
Verify directory accessibility via HTTPAttempt to access http://your-server/etc/extplorer/ and http://your-server/usr/ via curl or wget from a non-localhost source, or analyze access logs for such requestsAffected if HTTP requests to /etc/extplorer/ or /usr/ return directory listings or file contents instead of 403 Forbidden or 404 Not Found
A system is affected if eXtplorer is installed with a web server configuration that permits HTTP access to /usr/ or /etc/extplorer/ directories, allowing attackers to read sensitive system files.
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.
dbcve · scopedReview and correct the Makefile patch (debian/patches/debian-changes-2.1.0b6+dfsg-1 or debian/patches/adds-a-makefile.patch) and web server configuration to deny HTTP access to /usr/ and /etc/extplorer/ directories; verify system directories are no longer accessible via HTTP.
- Check your distribution's security updates for eXtplorer (Debian Security Advisory or Ubuntu Security Notice)
- Apply the distribution's security patch for CVE-2019-7305
- Verify that the web server configuration no longer allows access to /usr/ and /etc/extplorer/ directories
- Restart the web server to ensure the fix takes effect
- Audit the /usr/ and /etc/extplorer/ directories for any unauthorized access or data leakage that may have occurred
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7305 — 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-2019-7305 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