Skip to content
Web

CVE-2026-16051

9.8
Critical
EPSS 0.59%Patch availableAug 13, 2026

Replayable signed management request allows RCE via WPMUDEV Updates plugin (<5.0.1).

common questions

Is CVE-2026-16051 being exploited?

Not confirmed. CVE-2026-16051 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.59% probability of exploitation in the next 30 days.

How severe is CVE-2026-16051?

CVE-2026-16051 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-16051?

Yes. A fix has been recorded for CVE-2026-16051. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-16051 affect?

CVE-2026-16051 affects WPMUDEV Updates WordPress plugin < 5.0.1, WordPress sites using WPMUDEV remote management, Managed WP hosting running the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-16051?

Update plugin to 5.0.1+ immediately or disable remote management until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WPMUDEV Updates WordPress plugin < 5.0.1WordPress sites using WPMUDEV remote managementManaged WP hosting running the plugin
impact

Replay or use of a valid signed management request lets attacker install packages and execute arbitrary code (RCE), compromising sites and hosting.

action required

Immediate action required

affected versions
Unknown wpmudev-updates
  • affected< 5.0.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free