Content Fetcher
Limited data: Content Fetcher 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 | 20 |
| Security | 35 |
| Support | 70 |
| Reputation | 70 |
Quick answers
- Is Content Fetcher still maintained?
- No. Last release 11 Oct 2025, over 1 year ago. 11 Oct 2025 · wordpress.org
- Who owns Content Fetcher, 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 Content Fetcher removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is Content Fetcher safe?
- No. 1 known vulnerability has no fix in the current version. 31 Dec 2025 · Wordfence Intelligence
- Is the latest Content Fetcher update safe to install?
- No ownership change before 1.1. No one-star spike after it. 11 Oct 2025 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 31 Dec 2025 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.14 Jan 2026Evidence
- WarningMNT-2Tested up to WordPress 6.6.11, 5 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
- WarningMNT-1No release in 12 months (last release 11 Oct 2025). Plan a replacement if the plugin is important to your site.11 Oct 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
- 13 months ago
- Releases, 24 months
- 1
- Tested up to
- 6.6 vs 7.1
- Requires PHP
- not stated 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 | 1 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 11 Oct 2025. Tested up to 6.6, 5 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 3.2.
| 5 star | 3 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 1 |
| 1 star | 2 |
Security record
1 vulnerability in 24 months, 1 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 31 Dec 2025 | Content Fetcher <= 1.1 - Authenticated (Contributor+) Stored Cross-Site Scripting | 6.4 | <= 1.1 | 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
300+ 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.1 |
|---|---|
| Author | Ruhul Amin |
| Added | 30 May 2017 |
| Last updated | 11 Oct 2025 |
| Active installs | 300+ |
| Requires WordPress | not stated |
| Tested up to | 6.6.11 |
| Requires PHP | not stated |
| Category | not stated |
| Tags | scraper, data scrape, content scraper, content fectcher, content fetching |
Other plugins by this author: Techvila image optimization and CDN
Questions
Is Content Fetcher still maintained?
No. Last release 11 Oct 2025, over 1 year ago.
Who owns Content Fetcher, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Was Content Fetcher removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is Content Fetcher safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest Content Fetcher update safe to install?
No ownership change before 1.1. No one-star spike after it.