CVE-2017-11441
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 · uneditedThe WHM Upload Locale interface in cPanel before 56.0.51, 58.x before 58.0.52, 60.x before 60.0.45, 62.x before 62.0.27, 64.x before 64.0.33, and 66.x before 66.0.2 has XSS via a locale filename, aka SEC-297.
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 confidenceCross-site scripting (XSS) vulnerability in cPanel's WHM (Web Host Manager) Upload Locale interface allows injection of malicious scripts via unsanitized locale filenames. The vulnerability exists because user-supplied filename input is not properly escaped before rendering in the web 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<= 56.0.50= 58.0.3= 58.0.4= 58.0.5= 58.0.6= 58.0.7= 58.0.8= 58.0.11= 58.0.12= 58.0.13= 58.0.17= 58.0.19CVSS 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.
-
Check the installed WHM/cPanel versionLog in to WHM and navigate to 'Server Status' > 'cPanel WHM Service Status' or run command 'cat /usr/local/cpanel/version' in terminalAffected if The installed version matches any of the affected versions: 56.0.50 and below, or versions 58.0.3, 58.0.4, 58.0.5, 58.0.6, 58.0.7, 58.0.8, 58.0.11, 58.0.12, 58.0.13, 58.0.17, or 58.0.19
-
Verify access to the Upload Locale interfaceIn WHM, navigate to 'cPanel' > 'Locales' or search for 'Upload Locale' in the search bar to confirm the feature is present and accessibleAffected if The Upload Locale interface is accessible in WHM, indicating the vulnerable component is available for potential exploitation
-
Confirm WHM access levelDetermine if the user has sufficient privileges to access the Upload Locale feature - typically requires reseller or root administrator access in WHMAffected if The account has privileges to use the Upload Locale feature in WHM, which is required to trigger the XSS vulnerability
A system is affected if it runs an affected cPanel/WHM version (56.0.50 or below, or any of the listed 58.0.x versions) AND has the Upload Locale interface accessible to a user who can upload locale files with crafted filenames.
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 dataUpgrade cPanel to version 56.0.51, 58.0.52, 60.0.45, 62.0.27, 64.0.33, or 66.0.2 or later to obtain the patched version with proper input sanitization for locale filenames.
- 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-11441 — 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-11441 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