HomeWordPress vulnerabilitiesMainWP Child
MainWP Child vulnerabilities
MainWP Child has 4 known vulnerabilities in this database. The most recent published record is dated 27 Jul 2026.
- Known vulnerabilities
- 4
- Active installs
- 700,000+
- Latest version
- 6.2.1
- Last updated
- 30 Sep 2026
- Most recent
- 27 Jul 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Authentication bypass CVE-2026-12255 | High 8.1 | Before 6.1.2 | Fixed in 6.1.2 | 27 Jul 2026 |
| Privilege escalation CVE-2024-10783 | High 8.1 | Up to 5.2 | Fixed in a later version (latest 6.2.1) | 13 Dec 2024 |
| Sensitive data exposure CVE-2023-3132 | Medium 5.9 | Up to 4.4.1.1 | Fixed in a later version (latest 6.2.1) | 27 Jun 2023 |
| SQL injection CVE-2021-24877 | High 7.2 | Before 4.1.8 | Fixed in 4.1.8 | 23 Nov 2021 |
Read the published descriptions
- CVE-2026-12255, 27 Jul 2026
- The MainWP Child WordPress plugin before 6.1.2 does not verify the requester's identity in its site-registration request handler when password authentication has been disabled for the targeted account, allowing an unauthenticated attacker to obtain a valid authentication session as that account, including an administrator, by naming its login in a single registration request. CVE record
- CVE-2024-10783, 13 Dec 2024
- The MainWP Child - Securely Connects to the MainWP Dashboard to Manage Multiple Sites plugin for WordPress is vulnerable to privilege escalation due to a missing authorization checks on the register_site function in all versions up to, and including, 5.2 when a site is left in an unconfigured state. This makes it possible for unauthenticated attackers to log in as an administrator on instances where MainWP Child is not yet connected to the MainWP Dashboard. IMPORTANT: this only affects sites who have MainWP Child installed and have not yet connected to the MainWP Dashboard, and do not have the unique security ID feature enabled. Sites already connected to the MainWP Dashboard plugin and do not have the unique security ID feature enabled, are NOT affected and not required to upgrade. Please note versions up to 5.3.3 contained a patch, though a bypass was discovered and not addressed until version 5.3.4. CVE record
- CVE-2023-3132, 27 Jun 2023
- The MainWP Child plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 4.4.1.1 due to insufficient controls on the storage of back-up files. This makes it possible for unauthenticated attackers to extract sensitive data including the entire installations database if a backup occurs and the deletion of the back-up files fail. CVE record
- CVE-2021-24877, 23 Nov 2021
- The MainWP Child WordPress plugin before 4.1.8 does not validate the orderby and order parameter before using them in a SQL statement, leading to an SQL injection exploitable by high privilege users such as admin when the Backup and Staging by WP Time Capsule plugin is installed CVE record
What to do if you run MainWP Child
If you run MainWP Child, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new MainWP Child vulnerabilities
Free. We email you when a new vulnerability is published for MainWP Child, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.