Leadrebel
Limited data: Leadrebel has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Capped at 39: a vulnerability has no patch.
| Ownership | 100 |
|---|---|
| Maintenance | 0 |
| Security | 35 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is Leadrebel still maintained?
- No. Last release 3 Aug 2023, over 3 years ago. 3 Aug 2023 · wordpress.org
- Who owns Leadrebel, and has it changed hands?
- Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist. 4 Nov 2026 · SVN log
- Was Leadrebel removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is Leadrebel safe?
- No. 1 known vulnerability has no fix in the current version. 18 Feb 2026 · Wordfence Intelligence
- Is the latest Leadrebel update safe to install?
- No ownership change before 1.0.2. No one-star spike after it. 3 Aug 2023 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 18 Feb 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.4 Mar 2026Evidence
- CriticalMNT-1No release in 39 months (last release 3 Aug 2023). Plan a replacement if the plugin is important to your site.2 Aug 2024Evidence
- WarningMNT-2Tested up to WordPress 6.0.18, 11 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
No ownership change recorded. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Maintenance
- Last release
- 3 years ago
- Releases, 24 months
- 0
- Tested up to
- 6.0 vs 7.1
- Requires PHP
- 7.3 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 0 |
| Q2 2025 | 0 |
| Q3 2025 | 0 |
| Q4 2025 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 3 Aug 2023. Tested up to 6.0, 11 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews.
| 5 star | 0 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 0 |
Security record
1 vulnerability in 24 months, 1 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 18 Feb 2026 | Leadrebel <= 1.0.2 - Missing Authorization | 5.3 | <= 1.0.2 | No fix | n/a |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
50+ active installs. History builds with each weekly snapshot.
Momentum history builds with each snapshot.
Healthier alternatives
Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.
No healthier plugin in the same category yet.
Facts
| Version | 1.0.2 |
|---|---|
| Author | leadrebel |
| Added | 8 Nov 2022 |
| Last updated | 3 Aug 2023 |
| Active installs | 50+ |
| Requires WordPress | not stated |
| Tested up to | 6.0.18 |
| Requires PHP | 7.3 |
| Category | not stated |
| Tags | not stated |
Questions
Is Leadrebel still maintained?
No. Last release 3 Aug 2023, over 3 years ago.
Who owns Leadrebel, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Was Leadrebel removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is Leadrebel safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest Leadrebel update safe to install?
No ownership change before 1.0.2. No one-star spike after it.