CVE-2024-10783
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe MainWP Child WordPress plugin versions up to 5.2 (and patched versions 5.3.3 with bypass) contain a privilege escalation vulnerability in the register_site function. Unauthenticated attackers can register a site as an administrator on unconfigured MainWP Child installations where the unique security ID feature is not enabled and the plugin has not yet been connected to a MainWP Dashboard.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm MainWP Child plugin is installedLocate the MainWP Child plugin directory in the WordPress installation (typically wp-content/plugins/mainwp-child/) and verify the plugin files exist. In WordPress admin, check Plugins > Installed Plugins for MainWP Child.Affected if MainWP Child plugin is present on the WordPress site
-
Identify the installed MainWP Child versionOpen the main plugin file (usually mainwp-child.php) and read the version from the plugin header comment, or check the version listed in WordPress admin under Plugins > Installed Plugins.Affected if Version is 5.2 or lower, OR version 5.3.0 through 5.3.3 (vulnerable versions before 5.3.4)
-
Check if unique security ID feature is enabledIn WordPress admin, navigate to the MainWP Child settings page (orSettings > MainWP Child) and locate the unique security ID setting. Alternatively, check the wp_options table for the option named 'mainwp_child_uniqueId' or similar security ID option - if it exists and contains a value, the feature is enabled.Affected if Unique security ID feature is NOT enabled (option is missing, empty, or disabled)
-
Verify plugin connection status to MainWP DashboardCheck the WordPress admin dashboard for MainWP Child connection status. Look for indicators that the child site is connected to a parent Dashboard. This may appear on the MainWP Child settings page or as a dashboard widget. Alternatively, check wp_options for settings indicating an active connection to a Dashboard.Affected if Site shows as NOT connected to any MainWP Dashboard, or displays setup/connection pending status
The site is affected if MainWP Child is installed with a vulnerable version (5.2 or lower, or 5.3.0-5.3.3), the unique security ID feature is disabled or not configured, AND the plugin has not been connected to a MainWP Dashboard - meaning all three conditions must be true for the privilege escalation to be exploitable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate MainWP Child to version 5.3.4, or alternatively enable the unique security ID feature on installations that cannot update immediately. Sites already connected to a MainWP Dashboard or with unique security ID enabled are not affected.
5.3.4
- Backup your WordPress site before making any changes
- Update the MainWP Child plugin to version 5.3.4 or later through the WordPress plugin admin interface
- After updating, enable the unique security ID feature in the MainWP Child settings for additional protection
- If not already connected, connect the Child site to your MainWP Dashboard (this removes the vulnerability condition)
- Verify the plugin version shows 5.3.4 or higher in the installed plugins list
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10783 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10783 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data