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
Lifecycle Timeline
2DescriptionCVE.org
Editor Privilege Escalation in PublishPress Capabilities <= 2.45.0 versions.
AnalysisAI
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.
Technical ContextAI
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.
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.
More in Publishpress Capabilities
View allSame weakness CWE-266 – Incorrect Privilege Assignment
View allSame technique Privilege Escalation
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-53953
GHSA-m34w-rg3p-g738