CVE-2017-18418
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 66.0.2 allows stored XSS during WHM cPAddons file operations (SEC-265).
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in cPanel versions before 66.0.2. The flaw is specifically present in WHM cPAddons file operations, where malicious JavaScript can be injected and persistently stored, potentially executing in the browsers of other users accessing the cPanel 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< 66.0.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Verify cPanel installationCheck for cPanel directories or run: ls -la /usr/local/cpanel/ or whmapi1 versionAffected if The system does not have cPanel installed - this CVE only affects cPanel/WHM environments
-
Retrieve installed cPanel versionRun: /usr/local/cpanel/version or whmapi1 versionAffected if Unable to determine the cPanel version from the system
-
Compare version against vulnerable rangeCompare the installed version string to 66.0.2 - versions before 66.0.2 are affected (e.g., 66.0.1, 65.x, 64.x)Affected if Installed version is less than 66.0.2 (e.g., 66.0.1, 65.0.10, etc.) - the system falls within the vulnerable range
-
Confirm cPAddons feature is accessibleLog into WHM and navigate to Plugins section or check cPAddons module availability via: whmapi1 featurelist list or checking for cPAddons in WHM interfaceAffected if cPAddons is enabled and accessible in WHM - combined with version < 66.0.2, the stored XSS vulnerability is present
The environment is affected if cPanel/WHM is installed with a version lower than 66.0.2 and the cPAddons feature is accessible in WHM.
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 data66.0.2
Upgrade cPanel to version 66.0.2 or later to receive the vendor patch that addresses this stored XSS vulnerability in cPAddons file operations.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18418 — 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-18418 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