CVE-2016-10795
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 59.9999.145 allows stored XSS in the WHM tail_upcp2.cgi interface (SEC-156).
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 confidenceStored cross-site scripting (XSS) vulnerability in cPanel's WHM (Web Host Manager) interface, specifically in the tail_upcp2.cgi component. The vulnerability affects cPanel versions prior to 59.9999.145 and allows attackers to inject malicious scripts that are persisted and executed when users interact with the affected interface.
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.51.9999.98, < 11.52.6.6>= 11.54.0.0, < 11.54.0.29>= 55.9999.61, < 56.0.34>= 57.9999.48, < 58.0.29>= 59.9999.58, < 59.9999.145CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check installed cPanel version via command lineRun /usr/local/cpanel/cpanel -V or cat /var/cpanel/version to retrieve the installed cPanel version numberAffected if The version falls within any of these ranges: 11.51.9999.98 to 11.52.6.5, 11.54.0.0 to 11.54.0.28, 55.9999.61 to 56.0.33, 57.9999.48 to 58.0.28, or 59.9999.58 to 59.9999.144
-
Check installed cPanel version via WHM APIExecute whmapi1 version or access https://yourserver:2087/json-api/version to retrieve the cPanel versionAffected if The returned version matches any of the affected ranges listed above
-
Verify WHM (Web Host Manager) is accessibleConfirm that the WHM service is running and accessible on port 2087 (or 2086 for non-SSL). Check with systemctl status cpdavcd or by attempting to access the WHM login interfaceAffected if WHM is accessible and the cPanel version is within the affected ranges
-
Inspect tail_upcp2.cgi in WHMLocate the tail_upcp2.cgi script in the /usr/local/cpanel/base/whm/ directory (or equivalent path) and confirm it exists and is executableAffected if The script exists and the cPanel version is within the affected ranges, indicating the vulnerable component is present
If the installed cPanel version falls within any of the affected version ranges and WHM is accessible, the environment is vulnerable to stored XSS via the tail_upcp2.cgi component.
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.52.6.611.54.0.2956.0.34
Update cPanel to version 59.9999.145 or later to patch the stored XSS vulnerability in the WHM tail_upcp2.cgi interface. Until patched, restrict access to WHM administrative functions to trusted users only.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10795 — 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-10795 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