Vulnerability in WPMU DEV Dashboard (WordPress plugin) (CVE-2026-76581)
Summary
Vulnerability in WPMU DEV Dashboard (WordPress plugin) (CVE-2026-76581). Successful exploitation can lead to full system takeover. Exploitable via wdpsso_step1.
Original description
The description as published by the source.
The WPMU DEV Dashboard plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 5.0.1. This is due to inconsistent and ambiguous HMAC message construction between the unauthenticated wdpsso_step1 and wdpsso_step2 AJAX actions, where step 1 signs and discloses an unseparated concatenation of the token, state, redirect, and domain values, while step 2 verifies an unseparated concatenation that omits the domain field. This makes it possible for unauthenticated attackers, on sites connected to WPMU DEV with Hub SSO enabled and mapped to an administrator, to obtain a valid HMAC from step 1 and replay it to step 2 by moving the domain value into the redirect field, resulting in an authenticated administrator session.
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-76581 has been found in WPMU DEV Dashboard (WordPress plugin).
Attackers can target a specific entry point like wdpsso_step1 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 "WPMU DEV Dashboard (WordPress plugin) CVE-2026-76581" on the vendor's site.
CVE-2026-76581 (WPMU DEV Dashboard (WordPress plugin)) — CWE-347 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wdpsso_step1 / wdpsso_step2
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-347) exists in WPMU DEV Dashboard (WordPress plugin). Attackers reach the vulnerable code path via wdpsso_step1 without authentication.
Check the vendor advisory for the affected versions of WPMU DEV Dashboard (WordPress plugin). Attack surface: wdpsso_step1 / wdpsso_step2.
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・依存マニフェストで WPMU DEV Dashboard (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web security@wordfence.com
- web security@wordfence.com
- web nvd.nist.gov
- web wpmudev.com
- web github.com