Privilege Escalation in WordPress (CVE-2026-75971)
Summary
Vulnerability in WordPress (CVE-2026-75971). Successful exploitation can lead to full system takeover. Exploitable via import_start.
Original description
The description as published by the source.
The ShopEngine Elementor WooCommerce Builder Addon – All in One WooCommerce Solution plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.9.4. This is due to the rum_importer() function being registered on the WordPress core import_start action hook with no plugin-owned capability check and no allowlist filtering, causing arbitrary `` name/value pairs parsed from an attacker-supplied WXR import file to be passed directly to update_option(). This makes it possible for authenticated attackers, with Shop Manager-level access and above, to write arbitrary WordPress options — most critically setting users_can_register to 1 and default_role to administrator — enabling open self-registration of Administrator accounts and full site takeover. This is exploitable by Shop Manager-level users because WooCommerce grants that role the import capability, allowing it to reach the WordPress Importer flow that fires the import_start hook on which rum_importer() is registered, contrary to the assumption that the hook is restricted to Administrators.
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-75971 has been found in WordPress.
Attackers can target a specific entry point like import_start 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-75971" on the vendor's site.
CVE-2026-75971 (WordPress) — CWE-269 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: import_start / users_can_register / default_role / administrator
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 import_start.
Check the vendor advisory for the affected versions of WordPress. Attack surface: import_start / users_can_register / default_role / administrator.
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 でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web github.com