dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27366

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

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 · unedited
Unauthenticated Broken Access Control in MainWP Child <= 6.1.1 versions.

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 · moderate confidence

Unauthenticated broken access control vulnerability in MainWP Child plugin versions 6.1.1 and below allows attackers to access sensitive functionality without any credentials, potentially exposing administrative features or data.

MitigationUpdate MainWP Child plugin to the latest version (>6.1.1) to patch the access control flaw.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify MainWP Child plugin installation
    Check the WordPress plugins directory for the MainWP Child plugin files, or use WP-CLI: wp plugin list --name=mainwp-child --status=active
    Affected if The plugin is installed and active with version 6.1.1 or below
  2. Determine installed plugin version
    Review the plugin header in mainwp-child.php file or run: wp plugin list --name=mainwp-child --format=columns
    Affected if Version displayed is 6.1.1 or any version below it (e.g., 6.1.0, 6.0.x, etc.)
  3. Inspect authentication requirements on MainWP endpoints
    Review the plugin's ajax and admin-ajax handlers in the code to identify endpoints that should require authentication. Test accessing these endpoints without providing valid credentials.
    Affected if Sensitive MainWP endpoints respond without requiring authentication (no wp nonce verification, no current_user_can check, no API key validation)
  4. Check for unauthorized admin access patterns
    Review server access logs for requests to /wp-admin/admin-ajax.php or MainWP-specific REST endpoints originating from unauthenticated IP addresses, especially those triggering admin actions
    Affected if Log entries show unauthenticated requests successfully accessing administrative functionality that should require credentials

You are affected if the MainWP Child plugin is installed at version 6.1.1 or below and sensitive endpoints are accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update MainWP Child plugin to the latest version (>6.1.1) to patch the access control flaw.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27366 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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