# CVE-2026-4299: Missing authorization in MainWP Child Reports

> Authenticated subscribers can access sensitive activity logs via the Heartbeat API due to missing authorization checks in the MainWP Child Reports plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-xg9f-423r-vcp9

## What is CVE-2026-4299?

CVE-2026-4299 is a medium-severity missing authorization vulnerability in MainWP Child Reports, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-4299?


## How do I fix CVE-2026-4299?

No fix has been published for CVE-2026-4299 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4299 being exploited?

There is no known exploitation of CVE-2026-4299 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4299 and fix it if it is affected.

What it is: CVE-2026-4299 is a medium-severity missing authorization vulnerability in MainWP Child Reports, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4299 in the wild and no public exploit code.

Affected product: MainWP Child Reports. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4299/ (Markdown: https://insights.sbomify.com/CVE-2026-4299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4299
- OSV: https://osv.dev/vulnerability/CVE-2026-4299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4299/
Summaries are generated and may contain mistakes; the official description above is the record.