CVE-2026-75927: PublishPress Capabilities <= 2.50.0 - Authenticated (Editor+) Privilege Escalation to Fresh-Install Default Capability Grant
The PublishPress Capabilities – User Role Editor, Access Permissions, User Capabilities, Admin Menus plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.50.0. This is due to the addPluginCapabilities() function unconditionally granting the Editor role all 15 managecapabilities capabilities — including managecapabilities, managecapabilitiesroles, managecapabilitiessettings, and managecapabilitiesbackup — via a hard-coded $eligibleroles = ['administrator', 'editor'] assignment that runs automatically on the first admininit after plugin activation with no administrator opt-in, persisting the grants directly to the database. This makes it possible for authenticated attackers with Editor-level access to elevate their privileges to a site-wide capability manager, enabling them to create, rename, and delete non-system roles, modify capabilities of non-administrator roles, restore role backups, and write arbitrary plugin options whose names begin with cme, capsman, ppcapabilities, or presspermit via updateoption(). The escalation stops short of full Administrator access, as WordPress's mapmetacap layer still prevents the escalated Editor from granting administrator-only capabilities to other roles; however, all role-management and plugin-settings functionality gated solely on managecapabilities capabilities remains fully accessible.
Affected Software
Event History
Frequently Asked Questions
Which sites are exposed to this issue?
Sites running PublishPress Capabilities versions up to and including 2.50.0 are affected. Exploitation requires an authenticated user with the WordPress Editor role.
Is a non-default configuration or administrator action required for the capability grant?
No. On the first admin_init event after plugin activation, the plugin automatically treats both Administrator and Editor as eligible roles and grants the capabilities without administrator opt-in.
Does an Editor become a full WordPress Administrator?
No. The described escalation does not provide full Administrator access because WordPress map_meta_cap restrictions still apply. However, the Editor can manage non-administrator roles and capabilities, restore role backups, and modify certain plugin options.
What evidence could indicate that the grants have already been applied?
The capability grants persist directly in the database after the post-activation admin_init event. An affected site may show the Editor role holding manage_capabilities_* permissions, including manage_capabilities, manage_capabilities_roles, manage_capabilities_settings, and manage_capabilities_backup.
What option changes can an escalated Editor make?
They can write arbitrary plugin options through update_option() when the option name begins with cme_, capsman, pp_capabilities, or presspermit.