S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Jan 11, 2026

CVE-2016-15041 Scanner

Targets the mwp_setup_purchase_username parameter, allowing unauthenticated attackers to inject persistent scripts that execute in admin dashboards.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3.5k
Times Used
continuous scan runs
3.7k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2016-15041
6.1
CVSShigh
Exploitable remotely over the internet · no authentication required.

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
MainWP Dashboard: Self-hosted WordPress Management for Agenciesby mainwp
AFFECTED< 3.1.3SAFE ✓≥ 3.1.3
Updated Aug 22, 2026View on NVD →
Detail

MainWP Dashboard is a widely used WordPress plugin that enables administrators to manage multiple WordPress sites from a single, centralized dashboard. It is commonly employed by web developers, agencies, and site owners to streamline tasks like updates, backups, and performance monitoring across their network of sites. By consolidating management, it saves time and reduces the complexity of handling numerous WordPress installations individually. Given its role in overseeing critical site operations, the security of MainWP Dashboard is paramount for maintaining the integrity of managed websites.

The vulnerability identified as CVE-2016-15041 is a Stored Cross-Site Scripting (XSS) issue that affects MainWP Dashboard versions up to 3.1.2. This flaw arises from insufficient sanitization of user-supplied input and inadequate output escaping within the plugin. Specifically, the mwp_setup_purchase_username parameter fails to properly neutralize malicious content, allowing attackers to inject arbitrary JavaScript code. Stored XSS is particularly dangerous because the injected script is permanently stored on the server, affecting all users who access the compromised page.

Technically, the vulnerability is triggered through the mwp_setup_purchase_username parameter, which is part of the plugin's setup process. An unauthenticated attacker can craft a request containing malicious script code in this parameter. When the plugin processes and later displays this data without proper escaping, the script executes in the context of the victim's browser. This endpoint is typically accessible without authentication, making it a prime target for exploitation. The lack of input validation and output encoding at this specific point enables the persistent XSS attack.

If exploited, the impact can be severe. An attacker could steal session cookies, redirect users to phishing sites, deface the admin dashboard, or perform actions on behalf of an authenticated administrator. Since the script executes in the admin area, it could lead to full compromise of the WordPress site and potentially other sites managed through MainWP. This could result in data breaches, loss of control over multiple websites, and significant reputational damage. The CVSS score of 7.0 reflects the high severity and ease of exploitation of this vulnerability.

Solution Advice
  • Update MainWP Dashboard to version 3.1.3 or later, which includes a fix for CVE-2016-15041.
  • Implement strict input validation for all user-supplied data, especially the mwp_setup_purchase_username parameter.
  • Apply output escaping functions like esc_html() or wp_kses_post() when rendering user data in the admin dashboard.
  • Deploy a Content Security Policy (CSP) header to restrict script sources and mitigate XSS impacts.
  • Conduct regular security audits and vulnerability scans using tools like S4E to detect similar issues.
  • Educate administrators on safe coding practices and the importance of sanitizing inputs in custom plugins or themes.
  • Monitor server logs for suspicious activity targeting the mwp_setup_purchase_username parameter.
  • Consider using a Web Application Firewall (WAF) to block malicious payloads targeting known XSS vectors.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.