CVE-2026-3140

Ultimate Dashboard <= 3.8.14 - Cross-Site Request Forgery to Module Activation/Deactivation

2026-04-30 00:00
Nabil Irawan

Strategic Overview

Status
Patched in 3.8.15
Affected Version
<= 3.8.14
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-3140
View all Ultimate Dashboard – Custom WordPress Dashboard vulnerabilities

At a glance

CVE-2026-3140 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Ultimate Dashboard WordPress plugin, affecting versions <= 3.8.14. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.8.15; sites on affected versions should update now. Disclosed April 2026, reported by Nabil Irawan.

Vulnerability Overview

The Ultimate Dashboard plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.8.14. This is due to a flawed nonce validation conditional in the 'handle_module_actions' function. This makes it possible for unauthenticated attackers to toggle plugin modules on or off via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Ultimate Dashboard <= 3.8.14 carries this weakness at handle_module_actions, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Ultimate Dashboard the fix is 3.8.15: builds <= 3.8.14 are affected, anything from 3.8.15 onward is not.

Remediation

Update to version 3.8.15, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Ultimate Dashboard: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ultimate Dashboard 3.8.15 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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