CVE-2026-121970: medium-severity vulnerability in wphostingdev Pay with Vipps and MobilePay for…
Pay with Vipps and MobilePay for WooCommerce before 6.4.1 Webhook Signature Forgery
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
10Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.3
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.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
wphostingdev · Pay with Vipps and MobilePay for WooCommerceReferences
https://plugins.trac.wordpress.org/browser/woo-vipps/trunk/recurring/changelog.txthttps://plugins.trac.wordpress.org/browser/woo-vipps/trunk/recurring/includes/wc-vipps-recurring.phphttps://wordpress.org/plugins/woo-vipps/#developershttps://www.vulncheck.com/advisories/pay-with-vipps-and-mobilepay-for-woocommerce-before-webhook-signature-forgery