CVE-2018-20953
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 68.0.27 allows self XSS in the WHM listips interface (SEC-389).
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 confidenceSelf XSS vulnerability in cPanel's WHM listips interface affecting versions before 68.0.27. Self XSS requires a victim to manually inject malicious script into the vulnerable field through social engineering, rather than a direct attacker-controlled reflection.
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>= 61.9999.55, < 62.0.39>= 65.9999.38, < 66.0.35>= 67.9999.64, < 68.0.27CVSS 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 cPanel/WHM versionLog into WHM and navigate to Server Status > cPanel Version, or run command: /usr/local/cpanel/cpanel -VAffected if version is 61.9999.55 through 62.0.38, OR 65.9999.38 through 66.0.34, OR 67.9999.64 through 68.0.26
-
Verify WHM listips interface accessibilityAccess WHM and navigate to IP Functions > Show IP Address Usage (listips), or check if the /cpanelwebcall/ endpoint is exposedAffected if the WHM listips interface is accessible to user accounts who could inject content into the IP address fields
-
Confirm Self XSS vulnerable fields existIn WHM, go to IP Functions > Show IP Address Usage and inspect whether the IP address fields or related inputs accept and reflect unescaped HTML/JavaScript charactersAffected if the interface reflects user-supplied input in IP address fields without proper sanitization
You are affected if your cPanel version falls within 61.9999.55-62.0.38, 65.9999.38-66.0.34, or 67.9999.64-68.0.26 AND the WHM listips interface is accessible to users who could inject malicious scripts into input fields.
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 data62.0.3966.0.3568.0.27
Upgrade cPanel to version 68.0.27 or later to remediate. As a defensive measure, disable or restrict access to the WHM listips interface until the upgrade can be performed.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20953 — 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-2018-20953 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