CVE-2026-121970
Pay with Vipps and MobilePay for WooCommerce (woo-vipps) before …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- plugins.trac.wordpress.org/browser/woo-vipps/trunk/recurring/changelog.txt
- plugins.trac.wordpress.org/browser/woo-vipps/trunk/recurring/includes/wc-vipps-recurring.p
- wordpress.org/plugins/woo-vipps/#developers
- www.vulncheck.com/advisories/pay-with-vipps-and-mobilepay-for-woocommerce-before-webhook-s
- nvd.nist.gov/vuln/detail/CVE-2026-121970
- cve.org/CVERecord?id=CVE-2026-121970
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.