Privilege Escalation in WordPress (CVE-2026-111114)
Summary
Vulnerability in WordPress (CVE-2026-111114). Successful exploitation can lead to full system takeover. Exploitable via profile_update.
Original description
The description as published by the source.
The Nexter Extension – Security, Performance, Code Snippets & Site Toolkit plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.7.11 The vulnerability exists because the /?reset-view handler in role_switcher_to_view_admin_as() performs no nonce or capability check when the supplied username matches the authenticated caller, and because the plugin's only cleanup mechanism — the profile_update hook — does not fire when WordPress performs a bulk role change via wp-admin/users.php?action=promote, which calls WP_User::set_role() directly and leaves a stale administrator value in the nxtext_view_admin_original_role user meta. This makes it possible for authenticated attackers with Subscriber-level access or above to restore the stale stored Administrator role to their own account, effectively escalating their privileges to Administrator. Exploitation requires that the attacker's account previously held the Administrator role and used the View Admin Role Switcher feature before being demoted specifically through the bulk role-change control rather than the Edit User screen, as only the bulk path bypasses the profile_update hook that would otherwise have cleared the stored original role.
Source: GitHub Security Advisories (Global) 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-111114 has been found in WordPress.
Attackers can target a specific entry point like profile_update over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2026-111114" on the vendor's site.
CVE-2026-111114 (WordPress) — CWE-269 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: profile_update / administrator / nxtext_view_admin_original_role
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 profile_update.
Check the vendor advisory for the affected versions of WordPress. Attack surface: profile_update / administrator / nxtext_view_admin_original_role.
Severity: High (CVSS 7.5/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 でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web github.com