WP sIFR
Limited data: WP sIFR 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 WP sIFR still maintained?
- No. Last release 23 Mar 2009, over 17 years ago. 23 Mar 2009 · wordpress.org
- Who owns WP sIFR, and has it changed hands?
- No change recorded. 4 Nov 2026 · SVN log
- Was WP sIFR removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is WP sIFR safe?
- No. 1 known vulnerability has no fix in the current version. 29 Nov 2025 · Wordfence Intelligence
- Is the latest WP sIFR update safe to install?
- No ownership change before 0.6.8.1. No one-star spike after it. 23 Mar 2009 · Release history
Active signals
Facts we detected, with links to the source.
- CriticalSEC-2Vulnerability published 29 Nov 2025 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.13 Dec 2025Evidence
- CriticalMNT-1No release in 214 months (last release 23 Mar 2009). Plan a replacement if the plugin is important to your site.23 Mar 2010Evidence
- WarningMNT-2Tested up to WordPress 2.7.1, 44 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 since 2009.
Maintenance
- Last release
- 18 years ago
- Releases, 24 months
- 0
- Tested up to
- 2.7 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 23 Mar 2009. Tested up to 2.7, 44 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 |
|---|---|---|---|---|---|
| 29 Nov 2025 | sIFR <= 0.6.8.1 - Cross-Site Request Forgery | 4.3 | <= 0.6.8.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
40+ 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.8.1 |
|---|---|
| Author | Jupitercow |
| Added | 4 Mar 2009 |
| Last updated | 23 Mar 2009 |
| Active installs | 40+ |
| Requires WordPress | 2.5 |
| Tested up to | 2.7.1 |
| Requires PHP | not stated |
| Category | not stated |
| Tags | sifr, flash, fonts, scalable inman flash replacement |
Other plugins by this author: Gravity Forms: Post Updates, Sewn In Simple SEO, Sewn In XML Sitemap, Sewn In Template Log In, Sewn In Notifications, Sewn In Simple Social Optimization, Sewn In Post Delete
Questions
Is WP sIFR still maintained?
No. Last release 23 Mar 2009, over 17 years ago.
Who owns WP sIFR, and has it changed hands?
No change recorded.
Was WP sIFR removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is WP sIFR safe?
No. 1 known vulnerability has no fix in the current version.
Is the latest WP sIFR update safe to install?
No ownership change before 0.6.8.1. No one-star spike after it.