MainWP Dashboard <= 4.2.4.1 - Cross-Site Request Forgery

2022-06-21 00:00
Anonymous

Strategic Overview

Status
Patched in 4.2.5
Affected Plugin
MainWP Dashboard: Self-hosted WordPress Management for Agencies
Affected Version
<= 4.2.4.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all MainWP Dashboard: Self-hosted WordPress Management for Agencies vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MainWP Dashboard WordPress plugin, affecting versions <= 4.2.4.1. 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 4.2.5; sites on affected versions should update now. Disclosed June 2022.

Vulnerability Overview

The MainWP Dashboard plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.2.4.1. This is due to missing nonce validation on the render() and render_restore() function. This makes it possible for unauthenticated attackers to force site administrators to log into site's managed in the ManageWP portal 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)

MainWP Dashboard <= 4.2.4.1 carries this weakness at render(), 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 MainWP Dashboard the fix is 4.2.5: builds <= 4.2.4.1 are affected, anything from 4.2.5 onward is not.

Remediation

Update to version 4.2.5, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/a8a3ba35-3cc0-4a6b-bb96-6ae5a83e5ad6

Related records

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