CVE-2017-18406
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 · uneditedcPanel before 67.9999.103 allows SQL injection during eximstats processing (SEC-276).
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 confidenceSQL injection vulnerability in cPanel's eximstats processing component allows attackers to inject malicious SQL queries. Eximstats parses Exim mail server logs and generates statistics; the vulnerability exists in versions before 67.9999.103 and can be exploited 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>= 63.9999.74, < 64.0.40>= 65.9999.38, < 66.0.23>= 67.9999.64, < 67.9999.103CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Verify cPanel installation existsCheck for cPanel directories or version file: ls -la /usr/local/cpanel/ or cat /usr/local/cpanel/versionAffected if If the directory or version file does not exist, cPanel is not installed and this CVE does not apply
-
Retrieve installed cPanel versionRun: cat /usr/local/cpanel/version or whmapi1 get_cpanel_versionAffected if The command returns a version number that falls within any of these ranges: 63.9999.74 to 64.0.39, 65.9999.38 to 66.0.22, or 67.9999.64 to 67.9999.102
-
Confirm eximstats component is enabledCheck if eximstats service is running: systemctl status eximstats or service eximstats statusAffected if If eximstats is actively running, the vulnerable code path is present in the environment
-
Check eximstats database existenceInspect /var/cpanel/eximstats/ directory or check for eximstats MySQL database: mysql -e 'SHOW DATABASES LIKE "eximstats";'Affected if If the eximstats database exists and contains parsed mail log data, the vulnerable parsing logic is in use
A user is affected if cPanel is installed with a version matching any of the three affected ranges AND the eximstats component is enabled and processing Exim mail logs.
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 data64.0.4066.0.2367.9999.103
Upgrade cPanel to version 67.9999.103 or later to patch the SQL injection vulnerability in eximstats processing.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18406 — 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-2017-18406 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