Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

MainWP Child Reports Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with MainWP Child Reports, published between 2021 and 2026.

Dataset last synchronized: 2026-08-02 09:41:47 UTC

At a glance

Security Snapshot

4Total records
0Critical
2High
2Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2021-09-20First disclosure
2026-04-07Latest disclosure
4 of 4CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202111 records
202422 records
202611 records

Severity Breakdown

SeverityRecordsShare
High250%
Medium250%

Vulnerability-Type Breakdown

CSRF

2 records50%

First: 2024. Latest: 2024.

SQL Injection

1 record25%

First: 2021. Latest: 2021.

Missing Authorization

1 record25%

First: 2026. Latest: 2026.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 2.3
  • 2.2.1
  • 2.2
  • 2.0.8

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-2.2.6MainWP Child Reports <= 2.2.6 - Missing Authorization to Authenticated (Subscriber+) Information Disclosure via Heartbeat APIApril 7, 20262.3Medium
*-2.2MainWP Child Reports <= 2.2 - Cross-Site Request Forgery to Arbitrary Options UpdateAugust 7, 20242.2.1High
*-2.1.1MainWP Child Reports <= 2.1.1 - Cross-Site Request ForgeryApril 26, 20242.2Medium
*-2.0.7MainWP Child Reports <= 2.0.7 - Admin+ SQL InjectionSeptember 20, 20212.0.8High

Selected source records

Latest Records

MediumCVE-2026-4299

MainWP Child Reports <= 2.2.6 - Missing Authorization to Authenticated (Subscriber+) Information Disclosure via Heartbeat API

Published: April 7, 2026

Affected versions
*-2.2.6
Patched versions
2.3
Original Wordfence record
HighCVE-2024-7492

MainWP Child Reports <= 2.2 - Cross-Site Request Forgery to Arbitrary Options Update

Published: August 7, 2024

Affected versions
*-2.2
Patched versions
2.2.1
Original Wordfence record
MediumCVE-2024-33680

MainWP Child Reports <= 2.1.1 - Cross-Site Request Forgery

Published: April 26, 2024

Affected versions
*-2.1.1
Patched versions
2.2
Original Wordfence record
HighCVE-2021-24754

MainWP Child Reports <= 2.0.7 - Admin+ SQL Injection

Published: September 20, 2021

Affected versions
*-2.0.7
Patched versions
2.0.8
Original Wordfence record

Highest-Severity Records

HighCVE-2024-7492

MainWP Child Reports <= 2.2 - Cross-Site Request Forgery to Arbitrary Options Update

Published: August 7, 2024

Affected versions
*-2.2
Patched versions
2.2.1
Original Wordfence record
HighCVE-2021-24754

MainWP Child Reports <= 2.0.7 - Admin+ SQL Injection

Published: September 20, 2021

Affected versions
*-2.0.7
Patched versions
2.0.8
Original Wordfence record
MediumCVE-2026-4299

MainWP Child Reports <= 2.2.6 - Missing Authorization to Authenticated (Subscriber+) Information Disclosure via Heartbeat API

Published: April 7, 2026

Affected versions
*-2.2.6
Patched versions
2.3
Original Wordfence record
MediumCVE-2024-33680

MainWP Child Reports <= 2.1.1 - Cross-Site Request Forgery

Published: April 26, 2024

Affected versions
*-2.1.1
Patched versions
2.2
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory