Wp Vipergb
Approved changes feed: RSS · Atom
cpe:2.3:a:justin_k:wp-vipergb:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Justin K (f8483775-dcb9-57ff-a496-c0a575352991) |
|---|---|
| Product | Wp Vipergb (ead13341-8e91-5fa9-a8dc-477d310a0bd6) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-4409 |
vulnerable | 2026-06-08 06:50:17.719313 |
WP-ViperGB <= 1.6.1 - Cross-Site Request Forgery
MEDIUM (4.3)
The WP-ViperGB plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.6.1. This is due to missing or incorrect nonce validation when saving plugin settings. This makes it possible for unauthenticated attackers to change the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2024-05-24T02:31:03.095Z
Updated: 2026-04-08T17:30:35.082Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.