CVE-2016-10840
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 11.54.0.4 allows arbitrary code execution during locale duplication (SEC-72).
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 confidencecPanel before version 11.54.0.4 contains a vulnerability in its locale duplication feature that allows an attacker to execute arbitrary code. The flaw is exploitable without authentication or with low privileges, likely through command injection in the locale handling routine.
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.48.0.5, < 11.48.5.2>= 11.50.0.4, < 11.50.4.3>= 11.51.9999.98, < 11.52.2.4>= 11.54.0.0, < 11.54.0.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine installed cPanel versionRun the command: /usr/local/cpanel/cpanel -V or check the RPM package version with: rpm -q cpanelAffected if The version displayed falls within any of these ranges: 11.48.0.5 to 11.48.5.1, 11.50.0.4 to 11.50.4.2, 11.51.9999.98 to 11.52.2.3, or 11.54.0.0 to 11.54.0.3
-
Confirm cPanel build numberCheck the build number by running: whmapi1 get_cpanel_version or examining /usr/local/cpanel/versionAffected if The build number is earlier than 11.54.0.4 and matches one of the affected version branches (11.48.x, 11.50.x, 11.51.x, or 11.54.0.x)
-
Verify if unauthenticated locale API is exposedTest access to cPanel locale API endpoints without authentication: curl -k https://localhost:2087/execute/Locale/add_locale or similar locale manipulation endpointsAffected if The API responds without requiring authentication, indicating the vulnerable code path is exposed
You are affected if your cPanel version is 11.48.0.5 through 11.48.5.1, 11.50.0.4 through 11.50.4.2, 11.51.9999.98 through 11.52.2.3, or 11.54.0.0 through 11.54.0.3.
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.48.5.211.50.4.311.52.2.4
Update cPanel to version 11.54.0.4 or later to patch the arbitrary code execution vulnerability in the locale duplication feature.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10840 — 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-10840 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