CVE-2017-18456
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 62.0.17 allows self XSS in the WHM cPAddons showsecurity interface (SEC-217).
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 confidenceSelf XSS vulnerability in cPanel before version 62.0.17 allows authenticated users to inject malicious JavaScript through the WHM cPAddons showsecurity interface. The vulnerability executes in the context of the user's own session, making social engineering necessary for exploitation.
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>= 55.9999.61, < 56.0.46>= 57.9999.48, < 58.0.45>= 59.9999.58, < 60.0.39>= 61.9999.55, < 62.0.17CVSS 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 versionRun `cat /usr/local/cpanel/version` or `whmapi1 version` to retrieve the installed cPanel versionAffected if The version falls within any of these ranges: 55.9999.61 to 55.x.x, 57.9999.48 to 57.x.x, 59.9999.58 to 59.x.x, or 61.9999.55 to 61.x.x (versions prior to 62.0.17)
-
Verify WHM access is availableConfirm the system has WHM (Web Host Manager) interface enabled and you have an authenticated session with reseller or root privilegesAffected if The user has valid WHM credentials and can access the cPAddons interface
-
Confirm cPAddons module is presentLog into WHM and navigate to the cPAddons section, or check for the showsecurity interface at the cPAddons module path in the cPanel installationAffected if The cPAddons module with showsecurity functionality exists and is accessible in the WHM interface
You are affected if your cPanel version is prior to 62.0.17 AND you have authenticated WHM access with the cPAddons showsecurity interface available in your session.
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 data56.0.4658.0.4560.0.39
Update cPanel to version 62.0.17 or later to patch the XSS vulnerability in the cPAddons showsecurity interface.
- 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-2017-18456 — 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-2017-18456 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