CVE
CVE-2026-76581
wpmudev · WPMU DEV Dashboard
- First Reported
- Aug 29, 2026
- Latest Reported
- Aug 29, 2026
CVE Enrichment
- CVSS
- 9.8 CRITICAL
- EPSS
- 0.44%
- EPSS Percentile
- 38.02%
- CISA KEV
- Not listed
Description
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.
Technical Details
- CVSS Version
- 3.1
- CNA / NVD Source
- [email protected]
- Published
- 28-Aug-2026 15:16
- Last Modified
- 29-Aug-2026 03:19
- EPSS Date
- 2026-11-09
- CWE
- CWE-347
CVSS Vector
CVSS:3.1 AV:N /
AC:L /
PR:N /
UI:N /
S:U /
C:H /
I:H /
A:H
CNA Products / Version Status
- wpmudev · WPMU DEV Dashboard
Source: CNA · [email protected]
Default status: unaffected
0 ≤ version ≤ 5.0.1 — affected (semver)
References
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (1)
- CVE-2026-76581 (CVSS score: 9.8) – An authentication bypass flaw in the WPMU DEV Dashboard plugin that could allow an unauthenticated attacker, on sites connected to WPMU DEV with Hub Single-Sign On (SSO) enabled and Critical WordPress Plugin and Theme Flaws Could Enable Site Takeover or RCE
CVE (4)
MITRE ATT&CK (1)
Products (7)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
