CVE-2026-47365
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 · uneditedArgument injection vulnerability in WordPress Toolkit before 6.11.0 as used in cPanel & WHM, allows remote authenticated users to bypass cross-tenant authorization and execute arbitrary wp-toolkit CLI commands as another account.
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 confidenceArgument injection vulnerability in WordPress Toolkit before 6.11.0 allows authenticated remote users to bypass cross-tenant authorization and execute arbitrary wp-toolkit CLI commands as another account, enabling privilege escalation across tenants in multi-tenant cPanel & WHM environments.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Confirm WordPress Toolkit installationCheck if WordPress Toolkit is installed on the cPanel & WHM server. This is typically available as a cPanel plugin in multi-tenant hosting environments.Affected if WordPress Toolkit is not installed on the system
-
Identify WordPress Toolkit versionLocate and read the installed WordPress Toolkit version. In cPanel environments, this can often be found in the plugin metadata or by querying the package manager that installed the toolkit (e.g., rpm query for RHEL-based systems or dpkg for Debian-based).Affected if The installed version is lower than 6.11.0
-
Verify multi-tenant configurationDetermine if the cPanel & WHM environment hosts multiple tenant accounts. Check for the presence of multiple cPanel accounts on the server or within the hosting environment.Affected if The environment hosts multiple tenant accounts (multiple cPanel accounts)
-
Inspect for cross-tenant access attemptsReview WordPress Toolkit and wp-toolkit CLI command logs for any executed commands that originate from one tenant account but target resources belonging to another tenant account.Affected if Logs show wp-toolkit commands executed across different tenant accounts unexpectedly
The environment is affected if WordPress Toolkit is installed with a version before 6.11.0 on a multi-tenant cPanel & WHM system where untrusted users have access to WordPress Toolkit.
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.
dbcve · scopedUpgrade WordPress Toolkit to version 6.11.0 or later to patch the authorization bypass. In the meantime, restrict and monitor WordPress Toolkit access for untrusted users.
WordPress Toolkit 6.11.0 (included in cPanel & WHM update)
- Log in to WHM as the root user
- Navigate to 'Software' > 'Software Update' or run 'upcp' via command line to update cPanel & WHM
- Ensure the update includes WordPress Toolkit to version 6.11.0 or later
- After updating, verify the WordPress Toolkit version by accessing cPanel > WordPress Toolkit > Settings/About
- Confirm the installed version is 6.11.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47365 — 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-2026-47365 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