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.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 1.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Unknown Payable Payment Gateway for WooCommerce
fixed in 1.3.1
References 1
Questions about CVE-2026-94361
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: wpscan.com
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: wpscan.com
What should I do about it?
Update Payable Payment Gateway for WooCommerce to version 1.3.1, which is the listed fixed version.Source: wpscan.com
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: cve.now feed data