CVE-2024-10783: MainWP Child (WordPress plugin) · Missing Authorization
Affects MainWP Child (WordPress plugin)Source CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 8.1 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Dec 2024
Detectable: evidence found.
nuclei template: WordPress Plugin MainWP Child - Authentication Bypass
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mainwp MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites | Affected
| Fixed in– |
AI-suggested
Upgrade the MainWP Child plugin to version 5.3.4 or later, which contains the official fix addressing the bypass and missing authorization checks. Sites that are already connected to the MainWP Dashboard or have the unique security ID feature enabled are not vulnerable and do not require immediate action. Patch status is confirmed by the vendor's versioning information. Check the vendor advisory for the latest updates and ensure the plugin is configured and connected properly to the MainWP Dashboard.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/9156e536-a58e-4d78-b136-af8a9613ee23?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/mainwp-child/tags/5.2/class/class-mainwp-child.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/mainwp-child/tags/5.2/class/class-mainwp-connect.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/mainwp-child/tags/5.2/class/class-mainwp-connect.php (opens in a new tab)
- wordpress.org/plugins/mainwp-child/ (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3197586%40mainwp-child&new=3197586%40mainwp-child&sfp_email=&sfph_mail= (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3229741%40mainwp-child&new=3229741%40mainwp-child&sfp_email=&sfph_mail= (opens in a new tab)