Security readout for executives and security teams
Plain-English summary
A flaw in WPMU DEV Dashboard could let an attacker install and run arbitrary code on a WordPress site by obtaining or replaying a valid signed management request. Successful exploitation could expose site data, alter content, or disrupt operations. Versions before 5.0.1 are described as vulnerable.
Executive priority
Treat this as an immediate remediation priority because successful exploitation enables full remote code execution without ordinary user interaction. Identify affected WordPress sites, update them promptly, and investigate suspicious Hub installation activity. Current sources do not confirm active exploitation, so communicate urgency without claiming an ongoing campaign.
Technical view
The wpmudev-updates plugin before 5.0.1 lacks package-integrity verification and replay protection for Hub install actions. An attacker who obtains or replays a valid signed management request could install and execute arbitrary code remotely. The supplied CVSS 3.1 score is 9.8 and maps the issue to CWE-94.
Likely exposure
Exposure is most likely where wpmudev-updates versions earlier than 5.0.1 use the remote management interface. Exploitation requires access to, or replay of, a valid signed management request. The bundle does not establish how attackers might obtain such requests or whether all deployments expose the relevant interface.
Exploitation context
The supplied record is not listed as KEV, and the bundle provides no evidence of active exploitation. The WPScan reference carries an exploit tag, but that tag alone does not establish public exploit availability or observed attacks. Treat the flaw as highly consequential while distinguishing potential exploitation from confirmed activity.
Researcher notes
The core security failures are missing package-integrity verification and absent replay protection around signed Hub install requests. A valid signed request is an explicit prerequisite. The structured affected entry lists version “0” with default status unaffected, conflicting with the narrative statement that versions before 5.0.1 are vulnerable; verify vendor and WPScan records during scoping.
Mitigation direction
- Update wpmudev-updates to version 5.0.1 or later after confirming vendor-supported release guidance.
- Prioritize internet-reachable sites and deployments using the Hub remote management interface.
- If updating is delayed, consult vendor guidance about safely restricting or disabling remote management.
- Investigate unexpected package installations or code changes before returning potentially affected sites to normal operation.
Validation and detection
- Inventory every WordPress deployment and record the installed wpmudev-updates version.
- Confirm no deployment remains on a version earlier than 5.0.1.
- Review management records for unexpected or repeated Hub install actions.
- Inspect installed packages and site files for unexplained code changes associated with suspicious management activity.
- Verify the installed update came from an approved, trusted source.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-16051 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/8dae5fbf-2e9d-4978-b97d-a20e076cd309/CVE reference, WPScan · exploit, vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.