CVE-2025-2276

Ultimate Dashboard <= 3.8.7 - Missing Authorization to Authenticated (Subscriber+) Plugin Modules Activation/Deactivation

2025-03-25 11:05
mikemyers

Strategic Overview

Status
Patched in 3.8.8
Affected Version
<= 3.8.7
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-2276
View all Ultimate Dashboard – Custom WordPress Dashboard vulnerabilities

At a glance

CVE-2025-2276 is a medium-severity Missing Authorization vulnerability in the Ultimate Dashboard WordPress plugin, affecting versions <= 3.8.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.8.8; sites on affected versions should update now. Disclosed March 2025, reported by mikemyers.

Vulnerability Overview

The Ultimate Dashboard – Custom WordPress Dashboard plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the handle_module_actions function in all versions up to, and including, 3.8.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to activate/deactivate plugin modules.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Ultimate Dashboard <= 3.8.7 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Ultimate Dashboard the fix is 3.8.8: builds <= 3.8.7 are affected, anything from 3.8.8 onward is not.

Remediation

Update to version 3.8.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Ultimate Dashboard 3.8.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C