← WordPress Vulnerabilities
WordPress security by component

MainWP

MainWP is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jun 29, 2026; the highest CVE/CNA score is 7.6.

Plugin slug: mainwp

CVE-2026-57327: MainWP: A security weakness

MainWP is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 6.1.1.

PublishedJun 29, 2026
Known safe version6.1.2
Safe version
Jun 29, 2026 CVE-2026-57327
MainWP: A security weakness
MainWP is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 6.1.1.
6.1.2
CVE6.3
NVDPending
Mar 13, 2024 CVE-2024-1642
MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance: Cross-site request forgery
MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
See mitigation notes
CVE4.3
NVD4.3
Dec 20, 2023 CVE-2023-38519
MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance: SQL injection
MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE7.6
NVD4.9
Nov 22, 2023 CVE-2023-6164
MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance: A security weakness
MainWP Dashboard – WordPress Manager for Multiple Websites Maintenance is affected by a security weakness. Exploitation requires at least administrator-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE2.2
NVD4.8