Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain WordPress Editor credentials
-
DeliveryAuthenticate to target WordPress site
-
ExploitAccess PublishPress Capabilities settings interface
-
InstallExploit incorrect privilege assignment flaw
-
C2Escalate account to Administrator role
-
ExecuteInstall backdoor plugin or create rogue admin account
-
ImpactFull WordPress site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | Exploitation requires a valid WordPress account with Editor role (or higher, below Administrator) on a WordPress installation running PublishPress Capabilities plugin version 2.45.0 or earlier. The CVSS vector PR:H confirms that unauthenticated exploitation is not possible - an active authenticated session with elevated role access is mandatory. Sites where Editor accounts are exclusively granted to fully trusted internal staff face substantially reduced real-world risk compared to multi-tenant platforms, open-registration sites, or agencies managing client sites. The flaw is further scoped to installations where the PublishPress Capabilities plugin is installed and active; sites not using this plugin are not affected. No specific non-default configuration trigger is identified in available intelligence beyond the plugin being present and the attacker holding an Editor-level account. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H yields a base score of 7.2. The network attack vector and low complexity reflect that exploitation is straightforward over the web once the attacker is authenticated; the high-privilege prerequisite (PR:H - Editor role in WordPress context) is the primary limiting factor. No EPSS score was included in the provided intelligence, preventing probabilistic exploitation forecasting. The absence of both a CISA KEV listing and publicly known exploit code further moderates urgency for most deployments. However, real-world risk escalates significantly on multi-tenant WordPress environments - agencies, hosting platforms, membership sites - where Editor accounts are provisioned to users who are not fully trusted administrators. On such installations the effective risk approaches the full CVSS impact rating. CVSS scope is unchanged (S:U), confining direct impact to the compromised WordPress installation, though a full privilege escalation to Administrator enables secondary impacts such as plugin installation or credential harvesting that extend beyond the initial scope. |
| Exploit ScenarioDerived | An attacker who has obtained valid WordPress Editor credentials - through phishing, credential stuffing, or being a malicious insider - authenticates to the target site and navigates to the PublishPress Capabilities administration interface. The attacker exploits the incorrect privilege assignment flaw to elevate their own account to Administrator, then installs a malicious plugin or creates a backdoor admin account to maintain persistent access. No public exploit code has been identified at time of analysis, but the low attack complexity (AC:L) indicates that manual exploitation through the plugin's own UI is straightforward for any attacker familiar with WordPress administration. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 06, 2026
Editor-level privilege escalation in the PublishPress Capabilities WordPress plugin (versions ≤ 2.45.0) enables authenticated users holding an Editor role to exceed their intended permission boundary and gain unauthorized elevated capabilities. The root cause is incorrect privilege assignment (CWE-266) within the plugin's capability management logic, and with a CVSS base score of 7.2 (High) reflecting high impact across confidentiality, integrity, and availability, the flaw is most dangerous on multi-tenant or agency WordPress sites where Editor accounts are distributed to semi-trusted users. No public exploit code or CISA KEV listing has been identified at time of analysis.
RemediationAI
Upgrade PublishPress Capabilities to a version above 2.45.0 immediately; the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/capability-manager-enhanced/vulnerability/wordpress-publishpress-capabilities-plugin-2-45-0-privilege-escalation-vulnerability should be consulted to confirm the exact patched release, as no specific fix version number was provided in the available intelligence. As a compensating control pending upgrade, administrators should audit all Editor-role accounts and remove or demote any assigned to untrusted users, since exploitation requires an active Editor session. Additionally, review the PublishPress Capabilities settings panel for any suspicious capability assignments that may have already been made, and temporarily restrict access to the plugin's settings pages to Administrator accounts only via server-level controls (e.g., blocking the relevant admin-ajax or REST endpoints used by the plugin). Deactivating the plugin entirely is an option for sites that do not actively rely on its granular role management, with the trade-off that custom capability assignments managed by the plugin may revert to WordPress defaults.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PublishPress Capabilities (formerly capability-manager-enhanced) is a WordPress plugin that extends and manages the role-capability matrix built into WordPress core. WordPress enforces a hierarchical role model (Subscriber < Contributor < Author < Editor < Administrator), and plugins like PublishPress Capabilities expose a UI and programmatic interface to assign or modify these capabilities at a granular level. The affected versions (all releases up to and including 2.45.0, per CPE cpe:2.3:a:publishpress:publishpress_capabilities:*:*:*:*:*:*:*:*) contain a CWE-266 (Incorrect Privilege Assignment) flaw, meaning the plugin fails to properly enforce boundaries when an Editor-role user interacts with its capability assignment functions - allowing that user to assign themselves or others capabilities that exceed the Editor tier, up to and including Administrator-level access.
Know when Publishpress Capabilities gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Editor role access (PR:H) is required; exploitation occurs over the network via the WordPress admin interface with no interaction needed and full-system impact upon successful escalation.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Editor Privilege Escalation in PublishPress Capabilities <= 2.45.0 versions.
Executive ViewAI
The PublishPress Capabilities WordPress plugin (versions ≤2.45.0) enables authenticated Editor-level users to escalate privileges and gain unauthorized elevated capabilities through a capability assignment flaw, creating significant risk for organizations deploying multi-tenant WordPress sites or providing Editor access to semi-trusted personnel. The vulnerability impacts confidentiality, integrity, and availability across managed content. No vendor patch is currently available, requiring immediate interim mitigations.
Restrict Editor role assignment to only essential, pre-vetted personnel. Disable dangerous capabilities (publish_posts, manage_categories, edit_others_posts, manage_pages) for Editor accounts through WordPress Settings or plugin configuration. Implement comprehensive audit logging for all Editor account activities and suspicious permission-related requests. Require multi-factor authentication for all Editor-level accounts. Monitor capability assignments regularly for unauthorized changes. Consider transitioning sensitive workflows to Administrator-only roles with stricter controls until patch is released.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Publishpress Capabilities
View allCross-site request forgery in PublishPress Capabilities 2.50.1 and earlier lets an attacker lure a logged-in, sufficient
Privilege escalation in the PublishPress Capabilities WordPress plugin (slug capability-manager-enhanced) up to and incl
PublishPress Capabilities versions up to 2.31.0 contain an authorization bypass that allows authenticated users to explo
EUVD-2026-53953
GHSA-m34w-rg3p-g738
NVD
CVE.org
EPSS
VulDB
Exploit-DB