Skip to content
Fencer Intel
no cvss —

CVE-2026-103361 json

Payment Gateway via Valitor for WooCommerce < 1.9.41 - Unauthenticated Payment Bypass via a Shipped Default Verification Code

published 4h ago modified 3h ago also EUVD-2026-125978

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

The Payment Gateway via Valitor for WooCommerce WordPress plugin before 1.9.41 does not properly validate the authenticity of payment callbacks, relying on a verification secret that ships with a hard-coded default value used by every store that has not changed it, allowing unauthenticated attackers to forge a valid payment confirmation and mark arbitrary orders as paid.

Patch / fix

  • Unknown Payment Gateway via Valitor for WooCommerce 1.9.41

Is CVE-2026-103361 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploits and checks

  • wpscan.com https://wpscan.com/vulnerability/f368f380-c003-4701-82be-19990fa69818/ referenced PoC, tagged "exploit" by a source, unverified

Affected products

  • Unknown Payment Gateway via Valitor for WooCommerce

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.