CVE-2016-10858
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 11.54.0.0 allows unauthenticated arbitrary code execution via DNS NS entry poisoning (SEC-64).
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 confidencecPanel versions before 11.54.0.0 contain a critical vulnerability (SEC-64) that allows unauthenticated attackers to achieve arbitrary code execution through DNS NS (nameserver) entry poisoning. This enables complete system compromise without any authentication credentials.
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.48.0.5, < 11.48.4.8>= 11.50.0.4, < 11.50.3.1>= 11.51.9999.98, < 11.52.0.23>= 11.52.1.0, < 11.52.1.1CVSS 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.
-
Determine installed cPanel versionRun the command: /usr/local/cpanel/cpanel -V or whmapi1 versionAffected if The version number falls within any of these ranges: 11.48.0.5 to 11.48.4.7, 11.50.0.4 to 11.50.3.0, 11.51.9999.98 to 11.52.0.22, or 11.52.1.0
-
Verify if the server is configured as a nameserverCheck the DNS zone configuration files in /var/named/ or run: grep -r 'NS' /var/named/*.db 2>/dev/nullAffected if The server hosts DNS zones with NS records and the cPanel version is vulnerable
-
Confirm DNS service is runningRun: systemctl status named or service named statusAffected if The BIND/named DNS service is active and the cPanel version is vulnerable
You are affected if your installed cPanel version matches one of the four vulnerable version ranges AND your server is configured as a DNS nameserver with NS records.
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.48.4.811.50.3.111.52.0.23
Upgrade cPanel to version 11.54.0.0 or later. In the interim, implement DNSSEC and carefully monitor DNS records for unauthorized modifications that could facilitate the poisoning attack.
cPanel version 11.54.0.0 or later (preferably latest stable release)
- Identify the current cPanel version using 'whmapi1 version' or checking the cPanel dashboard
- Access WHM (Web Host Manager) as root administrator
- Navigate to 'cPanel >> Upgrade' or use the automatic update feature
- Initiate upgrade to cPanel version 11.54.0.0 or later (recommended: latest stable release)
- Allow the upgrade process to complete - this may take several minutes
- Verify the new version post-upgrade using 'whmapi1 version'
- Confirm the vulnerability is resolved by checking that the version is >= 11.54.0.0
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10858 — 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-10858 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