Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReconnaissance to identify a MainWP Child site with vulnerable version
-
DeliverySend crafted site-registration request targeting an admin login
-
ExploitPlugin omits identity verification due to disabled password authentication
-
ExecutionAttacker receives authenticated session as the admin
-
ImpactAttacker gains full access to the WordPress dashboard.
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | This vulnerability is only exploitable if the targeted account (e.g., an administrator) has password authentication explicitly disabled in the MainWP Child configuration. In default configurations, password authentication is enabled, making the attack infeasible. Additionally, the attacker must know or guess a valid username for the targeted account. |
| Impact | The CVSS v3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates a network-accessible vulnerability with high attack complexity, no privileges, no user interaction, and total compromise of confidentiality, integrity, and availability. No EPSS score is available, but the public exploit code and the ability to gain administrator access increase real-world risk. SSVC: exploitation is public (POC) but not confirmed active; the attack is automatable via a single HTTP request; technical impact is total. The high complexity stems from the prerequisite that password authentication must be disabled-a non-default configuration that limits exposure. For sites matching this condition, this is a critical priority; otherwise, it is a low-risk issue. |
| Exploit ScenarioDerived | An attacker identifies a WordPress site running a vulnerable MainWP Child plugin where the admin account has password authentication disabled. By sending a single unauthorized registration request containing that admin username, the attacker receives a valid session cookie and gains full administrative control over the site. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 27, 2026
MainWP Child plugin before 6.1.2 on WordPress allows unauthenticated attackers to hijack any account, including administrators, by sending a crafted site-registration request when password authentication is disabled for the targeted account. A publicly available exploit exists, but no active exploitation has been confirmed by CISA KEV.
RemediationAI
Upgrade MainWP Child to version 6.1.2 or later, as the vendor has released a fix. The patch is detailed in the WPScan advisory. If immediate patching is not possible, enforce password authentication for all accounts (especially administrators) in MainWP Child settings, or temporarily disable the plugin until the update can be applied. Note that re-enabling password authentication may impact users who deliberately disabled it for alternative authentication flows.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-287 (Improper Authentication) describes the root cause: the plugin's site-registration endpoint fails to verify the requester's identity under specific conditions. The underlying technology is a WordPress plugin that extends the MainWP management system; the vulnerable handler is part of the child-site registration mechanism. According to CPE cpe:2.3:a:unknown:mainwp_child:*:*:*:*:*:*:*:*, all versions before 6.1.2 are affected. When password-based login is disabled for a user account, the handler skips identity verification and directly creates a valid authentication session for the username supplied in the request.
Know when Mainwp Child gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Requires password auth disabled, so AC:H; no privileges or user interaction; total impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Mainwp Child
View allThe MainWP Child WordPress plugin before 4.1.8 does not validate the orderby and order parameter before using them in a
The MainWP Child Reports plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and inc
Broken access control in the MainWP Child WordPress plugin (versions 6.1.1 and earlier) allows remote attackers to invok
The MainWP Child plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including,
EUVD-2026-49065
GHSA-4ph4-5rpm-wrw9
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB