FeedWordPress Advanced Filters
Limited data: FeedWordPress Advanced Filters 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 | 70 |
| Reputation | 70 |
Quick answers
- Is FeedWordPress Advanced Filters still maintained?
- No. Last release 16 Dec 2014, over 11 years ago. 16 Dec 2014 · wordpress.org
- Who owns FeedWordPress Advanced Filters, 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 FeedWordPress Advanced Filters removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is FeedWordPress Advanced Filters safe?
- No. 1 known vulnerability has no fix in the current version. 27 Jan 2026 · Wordfence Intelligence
- Is the latest FeedWordPress Advanced Filters update safe to install?
- No ownership change before 0.6.2. No one-star spike after it. 16 Dec 2014 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 27 Jan 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.10 Feb 2026Evidence
- CriticalMNT-1No release in 144 months (last release 16 Dec 2014). Plan a replacement if the plugin is important to your site.16 Dec 2015Evidence
- WarningMNT-2Tested up to WordPress 4.0.38, 31 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
- 12 years ago
- Releases, 24 months
- 0
- Tested up to
- 4.0 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 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 16 Dec 2014. Tested up to 4.0, 31 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 2.5.
| 5 star | 3 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 5 |
Security record
1 vulnerability in 24 months, 1 with no fix in the current version.
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 27 Jan 2026 | FeedWordPress Advanced Filters <= 0.6.2 - Reflected Cross-Site Scripting | 6.1 | <= 0.6.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
100+ 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 | 0.6.2 |
|---|---|
| Author | Bas Schuiling |
| Added | 10 Apr 2013 |
| Last updated | 16 Dec 2014 |
| Active installs | 100+ |
| Requires WordPress | 3.0 |
| Tested up to | 4.0.38 |
| Requires PHP | not stated |
| Category | not stated |
| Tags | rss, Atom, feed, aggregation, syndication |
Other plugins by this author: Simple Category Icons, Welcome Mat
Questions
Is FeedWordPress Advanced Filters still maintained?
No. Last release 16 Dec 2014, over 11 years ago.
Who owns FeedWordPress Advanced Filters, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Was FeedWordPress Advanced Filters removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is FeedWordPress Advanced Filters safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest FeedWordPress Advanced Filters update safe to install?
No ownership change before 0.6.2. No one-star spike after it.