Skip to main content
VulnerabilityPublished

CVE-2026-121970: wphostingdev Pay with Vipps and MobilePay for WooCommerce · Improper Verification of Cryptographic Signature

Affects wphostingdev Pay with Vipps and MobilePay for WooCommerceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 6.4.1 when convenient.

Data as of 4 Nov 2026, 13:28 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.7
Patch
Available – fixed in 6.4.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade wphostingdev Pay with Vipps and MobilePay for WooCommerce to 6.4.1.

Affected software

ProductAffectedFixed in
wphostingdevPay with Vipps and MobilePay for WooCommerceAffected
  • >=5.0.0 <6.4.1
Fixed in
  • 6.4.1

AI-suggested

A fixed version 6.4.1 is available and should be applied to remediate this vulnerability. Upgrading to version 6.4.1 or later will resolve the improper signature verification issue. No additional mitigation steps are indicated by the vendor advisory.

Description

Pay with Vipps and MobilePay for WooCommerce versions from 5.0.0 up to but not including 6.4.1 contain a vulnerability in the recurring-payment webhook handler. The flaw is due to improper cryptographic signature verification when no local webhook secret is stored, allowing unauthenticated attackers to forge webhook requests. This can enable attackers to cancel active WooCommerce subscriptions by crafting specific webhook events. The issue is fixed in version 6.4.1.

References

Community reviews

Loading reviews…