Privilege Escalation in WordPress (CVE-2026-75927)
Summary
Vulnerability in WordPress (CVE-2026-75927). Successful exploitation can lead to full system takeover. Exploitable via manage_capabilities.
Original description
The description as published by the source.
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 manage_capabilities_* capabilities — including manage_capabilities, manage_capabilities_roles, manage_capabilities_settings, and manage_capabilities_backup — via a hard-coded $eligible_roles = ['administrator', 'editor'] assignment that runs automatically on the first admin_init 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, pp_capabilities, or presspermit via update_option(). The escalation stops short of full Administrator access, as WordPress's map_meta_cap 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 manage_capabilities_* capabilities remains fully accessible.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-75927 has been found in WordPress.
Attackers can target a specific entry point like manage_capabilities over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2026-75927" on the vendor's site.
CVE-2026-75927 (WordPress) — CWE-269 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: manage_capabilities / manage_capabilities_roles / manage_capabilities_settings / manage_capabilities_backup
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in WordPress. Attackers reach the vulnerable code path via manage_capabilities.
Check the vendor advisory for the affected versions of WordPress. Attack surface: manage_capabilities / manage_capabilities_roles / manage_capabilities_settings / manage_capabilities_backup.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WordPress を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。