Direct Payments for WooCommerce < 2.5.3 - Unauthenticated Cross-Customer Order Tampering via digages AJAX Actions
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-284.
Summary
The Direct Payments for WooCommerce WordPress plugin before 2.5.3 does not verify that the requester owns the targeted WooCommerce order in several unauthenticated AJAX handlers before changing its status and overwriting its payment metadata, allowing unauthenticated attackers to tamper with other customers' orders, including forging a "payment sent" state, overwriting the payment-method label, and attaching forged payment-proof files.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | Direct Payments for WooCommerce | before 2.5.3 | 2.5.3 | Patch available | CNA |
- Direct Payments for WooCommerce VendorUnknown Affected before 2.5.3 Fixed in 2.5.3 Patch available CNA
Remediation
- Fix · CNA Direct Payments for WooCommerce (Unknown) Fixed in 2.5.3
Timeline
- 2026-10-02 Threatist record created from CVE-2026-12966
- 2026-10-03 Alias added: GHSA-cp6p-3j8j-57c9
References
Sources
- CVE-2026-12966 · CVE Program
- CVE-2026-12966 · NVD
- FIRST EPSS
- GHSA-cp6p-3j8j-57c9 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences