CVE-2016-10807
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 certain denial-of-service outcomes via /scripts/killpvhost (SEC-112).
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 confidencecPanel before version 57.9999.54 contains a vulnerability in the /scripts/killpvhost script that allows an attacker to cause denial-of-service conditions. The specific DoS mechanism is not detailed in available sources, but the vulnerability is authenticated and involves resource consumption or service disruption via this administrative script.
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.51.9999.98, < 11.52.6.1>= 11.54.0.0, < 11.54.0.24>= 55.9999.61, < 56.0.15>= 57.9999.48, < 57.9999.54CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Verify cPanel is installedRun: ls -la /usr/local/cpanel/cpanel 2>/dev/null || rpm -qa | grep -i cpanel || whmapi1 versionAffected if cPanel is not installed on the system, so this CVE does not apply.
-
Retrieve cPanel versionExecute: /usr/local/cpanel/cpanel -V or grep version /usr/local/cpanel/versionAffected if Cannot determine cPanel version - manual inspection required.
-
Confirm /scripts/killpvhost existsCheck if the script exists: ls -la /scripts/killpvhostAffected if The script does not exist on this system.
-
Compare installed version to affected rangesMatch your installed version against: 11.50.0.4 to 11.50.6.2, 11.51.9999.98 to 11.52.6.1, 11.54.0.0 to 11.54.0.24, 55.9999.61 to 56.0.15, or 57.9999.48 to 57.9999.54. Versions in any of these ranges are affected.Affected if Your installed version falls within one of the affected version ranges.
If cPanel is installed and the version falls within any of the affected ranges (11.50.0.4-11.50.6.2, 11.51.9999.98-11.52.6.1, 11.54.0.0-11.54.0.24, 55.9999.61-56.0.15, or 57.9999.48-57.9999.54), the system is vulnerable to CVE-2016-10807.
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.50.6.211.52.6.111.54.0.24
Upgrade cPanel to version 57.9999.54 or later to remediate this vulnerability. Since the vulnerability allows DoS via an administrative script, ensure proper testing of the upgrade in a staging environment before production deployment.
- 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-10807 — 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-10807 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