CVE-2016-10817
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 57.9999.54 allows SQL Injection via the ModSecurity TailWatch log file (SEC-123).
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 ModSecurity TailWatch log file handling functionality allows attackers to inject malicious SQL queries through log file processing, potentially enabling unauthorized database access or manipulation.
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>= 11.50.0.4, < 11.50.6.2>= 11.52.6.0, < 11.52.6.1>= 11.54.0.0, < 11.54.0.24>= 56.0.1, < 56.0.15CVSS 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.0/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 cPanel versionRun 'whmapi1 version' or check /usr/local/cpanel/version fileAffected if Version falls within affected ranges: 11.50.0.4 to 11.50.6.1, 11.52.6.0, 11.54.0.0 to 11.54.0.23, or 56.0.1 to 56.0.14
-
Verify ModSecurity is enabledCheck WHM > ModSecurity Configuration or run grep ModSecurity /var/cpanel/cpanel.configAffected if ModSecurity is enabled and cPanel version is in affected range
-
Confirm TailWatch daemon is activeCheck service status via 'service chkservd status' or view in WHM Service StatusAffected if TailWatch/chkservd is running and version is vulnerable
System is affected if cPanel version is within the vulnerable ranges AND ModSecurity with TailWatch log processing is enabled
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 · scoped11.50.6.211.52.6.111.54.0.24
Upgrade cPanel to version 57.9999.54 or later to resolve the SQL injection vulnerability in the ModSecurity TailWatch log processing component.
cPanel version 57.9999.54 or later, or the branch-specific fixed versions: 11.50.6.2, 11.52.6.1, 11.54.0.24, or 56.0.15
- 1. Check current cPanel version by running: /usr/local/cpanel/cpanel -V
- 2. If version is 11.50.0.4 through 11.50.6.1, upgrade to 11.50.6.2 or later
- 3. If version is 11.52.6.0, upgrade to 11.52.6.1 or later
- 4. If version is 11.54.0.0 through 11.54.0.23, upgrade to 11.54.0.24 or later
- 5. If version is 56.0.1 through 56.0.14, upgrade to 56.0.15 or later
- 6. Alternatively, upgrade to version 57.9999.54 or later which contains the fix
- 7. Use /scripts/upcp or the cPanel WHM interface to perform the upgrade
- 8. After upgrade, verify the SQL injection vulnerability is resolved via the ModSecurity TailWatch log file functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10817 — 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-2016-10817 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