Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-75957 critical CVSS 9.8

Authentication Bypass in WordPress (CVE-2026-75957)

Summary

Authentication bypass in WordPress (CVE-2026-75957). Successful exploitation can lead to full system takeover. Exploitable via checkout_form.

Original description

The description as published by the source.

The Ultimate Multisite – WordPress Multisite SaaS & WaaS Platform plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 2.15.0 via the checkout_form parameter of the login_customer_after_checkout function. This is due to the publicly accessible wu_ajax_nopriv_wu_validate_form AJAX handler accepting a freely obtainable checkout nonce, and the checkout_form=wu-finish-checkout parameter causing get_validation_rules() to discard all validation rules while finish_checkout_form_fields() returns an empty step list — forcing is_last_step() to return true and routing the request directly into full order processing — after which maybe_create_customer() resolves the attacker-supplied email_address to an existing WordPress user ID without any authentication or ownership verification, and login_customer_after_checkout() calls wp_set_auth_cookie() for that user ID via a passwordless code path. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including a Network Super Admin — simply by knowing their email address. Exploitation requires that the targeted user account has no pre-existing Ultimate Multisite customer record; accounts such as a Network Super Admin on a fresh Multisite install, or any administrator or editor added before Ultimate Multisite was configured, satisfy this condition and are therefore exploitable.

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-75957 has been found in WordPress.
Attackers can target a specific entry point like checkout_form 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-75957" on the vendor's site.

CVE-2026-75957 (WordPress) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: checkout_form / login_customer_after_checkout / wu_ajax_nopriv_wu_validate_form / email_address
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.

❓ What is the problem

Authentication bypass (CWE-287) exists in WordPress. Attackers reach the vulnerable code path via checkout_form without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of WordPress. Attack surface: checkout_form / login_customer_after_checkout / wu_ajax_nopriv_wu_validate_form / email_address.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで WordPress を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details