WordPress plugin
WP-ViperGB security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 3 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
3Known vulnerabilities
- Critical0
- High0
- Medium3
- Low0
All WP-ViperGB vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Cross-Site Request Forgery ≤1.6.1Update to 1.6.2 | CVE-2024-4409 | |
| Medium6.1 | Cross-Site Scripting <1.3.16Update to 1.3.16 | CVE-2015-9356 | |
| Medium6.1 | Cross-Site Request Forgery to Cross-Site Scripting ≤1.3.10Update to 1.3.11 | CVE-2014-9460 |
- Medium4.3Cross-Site Request Forgery
≤1.6.1Update to 1.6.2
- Medium6.1Cross-Site Scripting
<1.3.16Update to 1.3.16
- Medium6.1Cross-Site Request Forgery to Cross-Site Scripting
≤1.3.10Update to 1.3.11
WP-ViperGB: common questions
Does WP-ViperGB have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in WP-ViperGB: 3 medium. None are known to affect version null.
How do I check which version of WP-ViperGB I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent WP-ViperGB vulnerability?
CVE-2024-4409, published May 23, 2024: WP-ViperGB <= 1.6.1 - Cross-Site Request Forgery. Severity: Medium (CVSS 4.3).
Is any WP-ViperGB vulnerability listed in CISA KEV?
No. None of the known WP-ViperGB vulnerabilities is currently listed in the CISA KEV catalog.