CVE-2016-10813
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 57.9999.54 allows self XSS during ftp account creation under addon domains (SEC-118).
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 Cross-Site Scripting (XSS) vulnerability in cPanel before version 57.9999.54. The flaw exists in the FTP account creation interface for addon domains, allowing an attacker to inject malicious JavaScript that executes in the user's own browser when viewing or managing the FTP account.
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.54.0.1, < 11.54.0.24>= 55.9999.61, < 56.0.15>= 57.9999.48, < 57.9999.54CVSS 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 your cPanel versionRun /usr/local/cpanel/cpanel -V or use the WHM API call whmapi1 get_cpanel_version to retrieve the installed cPanel versionAffected if The version falls within any of these ranges: 11.54.0.1 to 11.54.0.23, 55.9999.61 to 56.0.14, or 57.9999.48 to 57.9999.53
-
Identify addon domains configured on the accountLog in to cPanel and navigate to the Domains section or use the command line to list addon domains in /var/cpanel/userdata/Affected if Addon domains exist on the affected cPanel installation
-
Locate FTP accounts linked to addon domainsCheck the FTP accounts list in cPanel under the FTP section, or inspect /etc/proftpd/*.conf files for FTP accounts that reference addon domain pathsAffected if FTP accounts are configured for addon domains
-
Review recent FTP account creation logsExamine cPanel audit logs in /var/cpanel/logs/ or the main cPanel log for entries related to FTP account creation for addon domainsAffected if FTP accounts for addon domains were created using the vulnerable interface
You are affected if your cPanel version is within the affected ranges and you have created FTP accounts for addon domains through the cPanel interface.
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.54.0.2456.0.1557.9999.54
Update cPanel to version 57.9999.54 or later. Until patched, avoid creating FTP accounts for addon domains through the cPanel interface and implement input validation on the server side.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10813 — 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-10813 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