CVE-2016-10787
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 · uneditedThe Host Access Control feature in cPanel before 60.0.25 mishandles actionless host.deny entries (SEC-187).
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 confidenceThe Host Access Control feature in cPanel before version 60.0.25 improperly handles host.deny entries that lack an action specification, potentially allowing attackers to bypass intended access restrictions.
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.54.0.0, < 11.54.0.33>= 55.9999.61, < 56.0.39>= 57.9999.48, < 58.0.37>= 59.9999.58, < 60.0.25CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Determine cPanel versionRun 'cat /usr/local/cpanel/version' or check the cPanel version in WHM footerAffected if Version falls within ranges: 11.54.0.0-11.54.0.32, 55.9999.61-56.0.38, 57.9999.48-58.0.36, or 59.9999.58-60.0.24
-
Confirm Host Access Control is in useLocate the host.deny file typically in /etc/hosts.deny or check for Host Access Control configuration in WHM under Security CenterAffected if Host Access Control feature is enabled and host.deny file exists with entries
-
Inspect host.deny entries for missing action specificationsExamine the host.deny file for entries that lack an action field (such as entries without 'deny' or 'allow' directive)Affected if host.deny contains entries without a specified action (e.g., entries that only list IP addresses or ranges without a deny directive)
You are affected if running a cPanel version listed in the vulnerable ranges AND the Host Access Control feature is active with host.deny entries that lack action specifications.
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 data11.54.0.3356.0.3958.0.37
Update cPanel to version 60.0.25 or later to resolve the host.deny entry parsing issue.
- 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-2016-10787 — 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-10787 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