CVE-2024-10783 json
MainWP Child <= 5.3.3 - Missing Authorization to Unauthenticated Privilege Escalation
published 2024-12-13 22 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-33525
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- mainwp mainwp_child 5.3.4
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 22 mo ago
Exploit prediction
2.33% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template WordPress Plugin MainWP Child - Authentication Bypass nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- mainwp MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/9156e536-a58e-4d78-b136-af8a9613ee23?source=cve
- plugins.trac.wordpress.org /browser/mainwp-child/tags/5.2/class/class-mainwp-child.php#L76
- plugins.trac.wordpress.org /browser/mainwp-child/tags/5.2/class/class-mainwp-connect.php#L69
- plugins.trac.wordpress.org /browser/mainwp-child/tags/5.2/class/class-mainwp-connect.php#L788
- wordpress.org /plugins/mainwp-child/
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3197586%40mainwp-child&new=3197586%40mainwp-child&sfp_email=&sf
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3229741%40mainwp-child&new=3229741%40mainwp-child&sfp_email=&sf
Sources
- CVE List CVE-2024-10783
- NVD CVE-2024-10783
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.