dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4299

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The MainWP Child Reports plugin for WordPress is vulnerable to Missing Authorization in all versions up to and including 2.2.6. This is due to a missing capability check in the heartbeat_received() function in the Live_Update class. This makes it possible for authenticated attackers, with Subscriber-level access and above, to obtain MainWP Child Reports activity log entries (including action summaries, user information, IP addresses, and contextual data) via the WordPress Heartbeat API by sending a crafted heartbeat request with the 'wp-mainwp-stream-heartbeat' data key.

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 confidence

The MainWP Child Reports WordPress plugin versions up to 2.2.6 lack a capability check in the heartbeat_received() function within the Live_Update class. This allows any authenticated user with Subscriber-level access or higher to exploit the WordPress Heartbeat API by sending requests with the 'wp-mainwp-stream-heartbeat' data key, thereby bypassing authorization and accessing sensitive activity log entries containing action summaries, user information, IP addresses, and contextual data.

MitigationAdd a capability check (e.g., current_user_can('manage_options') or a custom capability) at the beginning of the heartbeat_received() function in the Live_Update class to verify the user has appropriate permissions before returning any activity log data. Alternatively, update to a patched version when released.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 Reports plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'MainWP Child Reports' or check the plugins directory for wp-content/plugins/ for a folder containing 'mainwp-child-reports'
    Affected if Plugin is not installed means not affected
  2. Check installed plugin version
    In Plugins list page, locate the version number displayed under the plugin name, or read the main plugin PHP file header for 'Version:' tag
    Affected if Version is present and less than 2.2.7 indicates vulnerability exists in that version
  3. Confirm plugin is active
    In WordPress admin > Plugins, check if the plugin shows as 'Active' under its status
    Affected if Plugin is active and version is below 2.2.7 means the vulnerability is exploitable
  4. Locate vulnerable heartbeat endpoint
    Check plugin files for class-live-update.php or similar file containing heartbeat_received() function in the Live_Update class, typically in includes/ directory
    Affected if File exists with heartbeat_received function without proper capability checks means vulnerable code is present
  5. Verify Heartbeat API is enabled
    In WordPress, the heartbeat API runs by default; check wp-config.php for DISABLE_HEARTBEAT constant set to true, or check if any heartbeat-related functionality is disabled
    Affected if Heartbeat is enabled (default) and plugin is vulnerable means exposure to the flaw exists

A site is affected if the MainWP Child Reports plugin is active with a version lower than 2.2.7 and the WordPress Heartbeat API is enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a capability check (e.g., current_user_can('manage_options') or a custom capability) at the beginning of the heartbeat_received() function in the Live_Update class to verify the user has appropriate permissions before returning any activity log data. Alternatively, update to a patched version when released.

Recommended fix Moderate confidence

MainWP Child Reports version 2.2.7 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'MainWP Child Reports' plugin
  4. Check if the current version is 2.2.6 or below
  5. If vulnerable, click 'Update Now' to install the latest version, or manually download the updated plugin from wordpress.org/plugins/mainwp-child-reports/ and upload it

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4299 — 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-4299 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