CVE-2026-4299: MainWP Child Reports <= 2.2.6 - Missing Authorization to Authenticated (Subscriber+) Information Disclosure via Heartbeat API
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 heartbeatreceived() function in the LiveUpdate 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MainWP Child Reportsto a version that resolves this vulnerability.Fixed in 2.2.6 - Compensating control
Mitigate exposure of sensitive activity log entries by preventing Subscriber+ users from accessing the WordPress Heartbeat API endpoint or by blocking heartbeat requests that include the 'wp-mainwp-stream-heartbeat' data key.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-4299?
CVE-2026-4299 is classified as a medium-severity vulnerability due to the potential disclosure of sensitive information.
How do I fix CVE-2026-4299?
To mitigate CVE-2026-4299, update the MainWP Child Reports plugin to version 2.2.7 or later.
Who is affected by CVE-2026-4299?
CVE-2026-4299 affects users of the MainWP Child Reports plugin for WordPress versions up to and including 2.2.6.
What type of attack is possible with CVE-2026-4299?
CVE-2026-4299 allows attackers to exploit missing authorization to access restricted information via the Heartbeat API.
Is there a known exploit for CVE-2026-4299?
As of now, there are no public reports of active exploits specifically targeting CVE-2026-4299.