MainWP Dashboard <= 4.6.0.1 - Cross-Site Request Forgery via posting_bulk
Strategic Overview
- Status
- Patched in 5.0
- Affected Version
<= 4.6.0.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-1642
At a glance
CVE-2024-1642 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MainWP Dashboard WordPress plugin, affecting versions <= 4.6.0.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 5.0; sites on affected versions should update now. Disclosed February 2024, reported by Krzysztof Zając.
Vulnerability Overview
The MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.6.0.1. This is due to missing or incorrect nonce validation on the 'posting_bulk' function. This makes it possible for unauthenticated attackers to delete arbitrary posts 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.6.0.1 carries this weakness at posting_bulk, 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 5.0: builds <= 4.6.0.1 are affected, anything from 5.0 onward is not.
Remediation
Update to version 5.0, 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 5.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in MainWP Dashboard: Self-hosted WordPress Management for Agencies
- 7.3MainWP Dashboard and MainWP Child <= 2.0.22 Unspecified Vulnerability
- 7.2CVE-2023-38519: MainWP <= 4.4.3.3 SQL Injection
CVE-2023-38519 - 7.2CVE-2016-15041: MainWP Dashboard Stored XSS
CVE-2016-15041 - 4.3CVE-2026-57327: MainWP Dashboard Missing Authorization
CVE-2026-57327 - 2.2CVE-2023-6164: MainWP Dashboard <= 4.5.1.2 CSS Injection
CVE-2023-6164
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C