MainWP Dashboard – The Private WordPress Manager for Multiple Website Maintenance Plugin <= 3.1.2 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 3.1.3
- Affected Version
< 3.1.3- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2016-15041
At a glance
CVE-2016-15041 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the MainWP Dashboard WordPress plugin, affecting versions < 3.1.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.3; sites on affected versions should update now. Disclosed April 2016, reported by Jouko Pynnöne.
Vulnerability Overview
The MainWP Dashboard – The Private WordPress Manager for Multiple Website Maintenance plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘mwp_setup_purchase_username’ parameter in versions up to, and including, 3.1.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
MainWP Dashboard < 3.1.3 carries this weakness at mwp_setup_purchase_username, and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For MainWP Dashboard the fix is 3.1.3: builds < 3.1.3 are affected, anything from 3.1.3 onward is not.
Remediation
Update to version 3.1.3, 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 3.1.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
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 - 4.3CVE-2026-57327: MainWP Dashboard Missing Authorization
CVE-2026-57327 - 4.3CVE-2024-1642: MainWP Dashboard <= 4.6.0.1 Cross-Site Request Forgery
CVE-2024-1642 - 4.3MainWP Dashboard <= 4.2.4.1 Cross-Site Request Forgery
- 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