MainWP Child Reports

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 82% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Refined from the date this plugin crossed into its current band.

Modeled from public signals only; the real figure depends on pricing and conversion we cannot see. The range spans more than 10x because wp.org publishes install counts as broad bands, and conversion and price compound on top. Read the midpoint as an order of magnitude, not a valuation.

1. ★★★★★ moesioli

   5.6y ago

   works like it should with many individual options

   Read on wp.org ↗
2. ★★★★★ kwebdesign

   6.6y ago

   I’ve been using the client reports for about a year now and our clients finally see some value in the support fees we charge. Oh and the support is great! This topic was modified 6 years, 5 months ago by kwebdesign.

   Read on wp.org ↗
3. ★★★★★ jrundle13

   8.2y ago

   Once I finished installation and setup and grab the subscription – I now email out monthly reports, just to show my clients how much work I do for them each week – which of course is much easier now that I use MainWP Dashboard with all my websites I manage.

   Read on wp.org ↗
4. ★★★★★ voneff

   9.0y ago

   It works just fine for me and helps me generate these MainWP reports which my clients really appreciate – and which help me bill my maintenance work. Clients usually don’t get that websites need updates – but when you can document the stuff you’re doing, they get the idea.

   Read on wp.org ↗
5. ★★★★★ 1rico1

   9.4y ago

   not working. This topic was modified 9 years, 3 months ago by 1rico1.

   Read on wp.org ↗
6. ★★★★★ dilusionz

   10.8y ago

   fixed sucuri child reporting blank issue if anyone else had this problem.. MainWP rocks!

   Read on wp.org ↗

Recent releases and news for this plugin

1. — Version 2.3.1 Fixed: Prevented null metadata from being saved during record insertion, improving data integrity and avoiding PHP warnings., Added: Support for logging updates performed by the WordPress auto-updater. 2.3.1
2. — Version 2.3 Security: Improved authorization checks in the Heartbeat API to prevent unintended access to Child Reports data by authenticated users with lower-level permissions. Updating to version 2.3 is recommended. (CVE-2026-4299) 2.3
3. — Version 2.2.6 Fixed: Resolved an issue where certain context exclusion rules would not be saved properly, improving compatibility with third-party plugins. (#809) 2.2.6
4. — Version 2.2.5 Fixed: Resolved deprecation warning related to the translate_meta_boxes function 2.2.5
5. — Version 2.2.4 Fixed: Resolved PHP Warning that occurred due to conflict with the WP Pusher plugin. Fixed: Eliminated PHP Error caused by compatibility issues with the WP All Import plugin. Updated: Implemented wp_get_wp_version() meth 2.2.4
6. — Version 2.2.3 Added: Value sanitization during the process of saving Network settings to enhance security and data integrity. 2.2.3

4 disclosed vulnerabilities on record for this plugin, all fixed in the current version. Sites on older versions stay exposed until they update.

1. Medium · 5.3 MainWP Child Reports <= 2.2.6 - Missing Authorization to Authenticated (Subscriber+) Information Disclosure via Heartbeat API ↗
   2026-04-07 CVE-2026-4299 Missing Authorization Affects <= 2.2.6 Patched in 2.3
2. High · 8.8 MainWP Child Reports <= 2.2 - Cross-Site Request Forgery to Arbitrary Options Update ↗
   2024-08-07 CVE-2024-7492 Cross-Site Request Forgery (CSRF) Affects <= 2.2 Patched in 2.2.1
3. Medium · 4.3 MainWP Child Reports <= 2.1.1 - Cross-Site Request Forgery ↗
   2024-04-26 CVE-2024-33680 Cross-Site Request Forgery (CSRF) Affects <= 2.1.1 Patched in 2.2
4. High · 7.2 MainWP Child Reports <= 2.0.7 - Admin+ SQL Injection ↗
   2021-09-20 CVE-2021-24754 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') Affects <= 2.0.7 Patched in 2.0.8

Automated install-time checks, tested on PHP 8.1.12 · WP 7.0.1

Translated into 10 languages, 4 at 90% or more

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2025-03-07 90K+ → 100K+ up after 275 days in tier
2. 2024-06-05 80K+ → 90K+ up after 182 days in tier
3. 2023-12-06 70K+ → 80K+ up after 183 days in tier
4. 2023-06-06 60K+ → 70K+ up after 178 days in tier
5. 2022-12-10 50K+ → 60K+ up after 7 days in tier
6. 2022-12-03 60K+ → 50K+ down after 1 days in tier
7. 2022-12-02 50K+ → 60K+ up after 3 days in tier
8. 2022-11-29 60K+ → 50K+ down after 10 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

• MainWP Key Maker 4K+ installs · 4.0★ · 2 shared tags B
• MainWP Post SMTP Extension – Easily Manage WP SMTP Setup for All Sites in One Place 300+ installs · 4.0★ · 2 shared tags B
• Update Brief for MainWP 30+ installs · 3.6★ · 2 shared tags B
• SEOPress for MainWP 900+ installs · 3.6★ · 1 shared tag C
• WP Compress for MainWP 700+ installs · 4.1★ · 1 shared tag B
• Security Ninja For MainWP 500+ installs · 4.0★ · 1 shared tag B

Embed this report card

Drop a live Pulse card for MainWP Child Reports into a readme, a review or a deck. It updates itself.

MainWP Child Reports: 100K+ active installs, 4.3★ (6 reviews). Plugin Pulse (WP Mayor), as of 2026-08-25. https://plugins.wpmayor.com/plugin/mainwp-child-reports