WP-ViperGB
Limited data: WP-ViperGB has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Capped at 59: a Critical signal is open.
| Ownership | 100 |
|---|---|
| Maintenance | 0 |
| Security | 100 |
| Support | 70 |
| Reputation | 70 |
Quick answers
- Is WP-ViperGB still maintained?
- No. Last release 23 May 2024, over 2 years ago. 23 May 2024 · wordpress.org
- Who owns WP-ViperGB, 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 WP-ViperGB removed from wordpress.org?
- No. Listed on wordpress.org as of 4 Nov 2026. 4 Nov 2026 · wordpress.org
- Is WP-ViperGB safe?
- 3 known vulnerabilities, all fixed (latest in 1.6.2). Not on the exploited list. 23 May 2024 · Wordfence Intelligence
- Is the latest WP-ViperGB update safe to install?
- No ownership change before 1.6.2. No one-star spike after it. 23 May 2024 · Release history
Active signals
Facts we detected, with links to the source.
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
- 2 years ago
- Releases, 24 months
- 0
- Tested up to
- 6.5 vs 7.1
- Requires PHP
- not stated supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 1 |
| 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 May 2024. Tested up to 6.5, 6 major versions behind WordPress 7.1.
Reputation
Last 90 days: no reviews. Lifetime: 4.5.
| 5 star | 3 |
|---|---|
| 4 star | 0 |
| 3 star | 1 |
| 2 star | 0 |
| 1 star | 0 |
Security record
3 vulnerabilities on record, all patched (latest fixed in 1.6.2).
Show 3 patched vulnerabilities
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 23 May 2024 | WP-ViperGB <= 1.6.1 - Cross-Site Request Forgery | 4.3 | <= 1.6.1 | 1.6.2 | Patched before disclosure |
| 20 Apr 2015 | Viper GuestBook <= 1.3.15 - Cross-Site Scripting | 6.1 | < 1.3.16 | 1.3.16 | n/a |
| 12 Dec 2014 | WP-ViperGB <= 1.3.10 - Cross-Site Request Forgery to Cross-Site Scripting | 6.1 | <= 1.3.10 | 1.3.11 | 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.6.2 |
|---|---|
| Author | JK |
| Added | 8 Mar 2010 |
| Last updated | 23 May 2024 |
| Active installs | 300+ |
| Requires WordPress | 2.5 |
| Tested up to | 6.5.14 |
| Requires PHP | not stated |
| Category | not stated |
| Tags | vipergb, guestbook, viper guestbook |
Other plugins by this author: Social Photo Fetcher, WP Social AutoConnect
Questions
Is WP-ViperGB still maintained?
No. Last release 23 May 2024, over 2 years ago.
Who owns WP-ViperGB, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.
Was WP-ViperGB removed from wordpress.org?
No. Listed on wordpress.org as of 4 Nov 2026.
Is WP-ViperGB safe?
3 known vulnerabilities, all fixed (latest in 1.6.2). Not on the exploited list.
Is the latest WP-ViperGB update safe to install?
No ownership change before 1.6.2. No one-star spike after it.