Pay With Vipps And Mobilepay For Woocommerce
Approved changes feed: RSS · Atom
cpe:2.3:a:wphostingdev:pay_with_vipps_and_mobilepay_for_woocommerce:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Wphostingdev (923b0c6e-ca1e-5fe5-b295-22b66049686c) |
|---|---|
| Product | Pay With Vipps And Mobilepay For Woocommerce (40735e2b-fb58-53d1-8e27-aa2910305026) |
| 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-2026-121970 |
vulnerable | 2026-11-04 14:25:23.942524 |
Pay with Vipps and MobilePay for WooCommerce before 6.4.1 Webhook Signature Forgery
LOW (3.7)
Pay with Vipps and MobilePay for WooCommerce (woo-vipps) before 6.4.1 contains an improper cryptographic signature verification vulnerability in the recurring-payment webhook handler that allows unauthenticated attackers to forge webhook requests when no local webhook secret is stored, because the code fails to return on an empty secret and computes an HMAC keyed with an empty string using a loose == comparison instead of hash_equals. Attackers can craft a recurring.agreement-stopped.v1 event with a known agreementId and a matching empty-key signature to cancel a victim's active WooCommerce subscription.
Published: 2026-11-04T13:01:41.868Z
Updated: 2026-11-04T18:47:15.201Z Reference links
|
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.