CVE-2016-10822
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 55.9999.141 allows self XSS in X3 Reseller Branding Images (SEC-88).
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's X3 Reseller Branding Images feature allows attackers to inject malicious scripts via the image branding fields. The vulnerability affects cPanel versions before 55.9999.141 and requires social engineering to trick users into pasting malicious code into the affected field.
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.50.0.4, < 11.50.5.2>= 11.51.9999.98, < 11.52.4.1>= 11.54.0.0, < 11.54.0.20>= 55.9999.61, < 55.9999.141CVSS 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 cPanel versionRun `whmapi1 version` or `/usr/local/cpanel/cpanel -V` to retrieve the installed cPanel version numberAffected if The installed version falls within any of these ranges: 11.50.0.4 to 11.50.5.2, 11.51.9999.98 to 11.52.4.1, 11.54.0.0 to 11.54.0.20, or 55.9999.61 to 55.9999.141
-
Confirm X3 theme is activeLog into cPanel as a reseller and navigate to the interface. The X3 theme presents the Reseller Branding Images feature in the account management section. Check which theme is active via the account's cPanel theme settingAffected if The X3 theme is in use and the Reseller Branding Images feature is accessible to the account
-
Identify reseller accountsCheck WHM for reseller accounts using `whmapi1 listresellers` or by viewing reseller privileges in the account management interfaceAffected if Any reseller accounts exist on the system, as these have access to the vulnerable branding image fields
-
Locate the vulnerable fieldsIn cPanel with X3 theme, a reseller can access Reseller Branding Images under the account's customization or branding section. These fields accept image-related values that can contain script contentAffected if The Reseller Branding Images fields are present and accept user-supplied input without proper sanitization
The environment is affected if cPanel version falls within any of the four affected version ranges AND the X3 theme is active with reseller accounts that have access to the Reseller Branding Images feature.
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.50.5.211.52.4.111.54.0.20
Update cPanel to version 55.9999.141 or later. Until then, warn users not to paste untrusted content into the Reseller Branding Images fields.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10822 — 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-10822 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