Privilege Escalation in WordPress (CVE-2026-104748)
Summary
Vulnerability in WordPress (CVE-2026-104748). Successful exploitation can lead to full system takeover. Exploitable via wp_ajax_nopriv_simpleform_wp_register.
Original description
The description as published by the source.
The SimpleForm – Form Maker to Chat Apps with Quiz, Poll and Multi Lead Notifications plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.10.0 This is due to the wp_ajax_nopriv_simpleform_wp_register AJAX action lacking any capability check for role assignment and the save_custom_fields_to_user_meta() function using an exclusion list that omits wp_capabilities, combined with get_form_settings() returning a hard-coded defaults array that unconditionally enables meta writing regardless of the supplied form_id. This makes it possible for unauthenticated attackers to create a new Administrator-level WordPress account by supplying wp_capabilities[administrator]=1 alongside standard registration fields. The nonce required by the endpoint is publicly emitted into the front_end_data JavaScript object on every front-end page via wp_enqueue_scripts, making it trivially obtainable by any unauthenticated visitor before submitting the malicious request.
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-104748 has been found in WordPress.
Attackers can target a specific entry point like wp_ajax_nopriv_simpleform_wp_register over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WordPress CVE-2026-104748" on the vendor's site.
CVE-2026-104748 (WordPress) — CWE-269 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wp_ajax_nopriv_simpleform_wp_register / wp_capabilities / form_id / front_end_data
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 wp_ajax_nopriv_simpleform_wp_register without authentication.
Check the vendor advisory for the affected versions of WordPress. Attack surface: wp_ajax_nopriv_simpleform_wp_register / wp_capabilities / form_id / front_end_data.
Severity: Critical (CVSS 9.8/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 でアラート再発が無いか継続監視。