Unauthenticated order tampering via unchecked AJAX ownership
Published Aug 1, 2026 · Updated Aug 1, 2026
Improper authorization in Direct Payments for WooCommerce before 2.5.3 allows remote attackers to alter other customers' orders through AJAX. Several wp_ajax_nopriv_digages_* handlers trust an attacker-supplied order_id after checking only a nonce that every anonymous front-end visitor can obtain. No account is required; exploitation can forge a payment-sent status, replace the payment-method label, and attach a forged proof file.
Summary
What happened
Improper authorization in Direct Payments for WooCommerce before 2.5.3 allows remote attackers to alter other customers' orders through AJAX. Several wp_ajax_nopriv_digages_* handlers trust an attacker-supplied order_id after checking only a nonce that every anonymous front-end visitor can obtain. No account is required; exploitation can forge a payment-sent status, replace the payment-method label, and attach a forged proof file.
The record
- CVE
- CVE-2026-12966
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Digages
- Product
- Direct Payments for WooCommerce
- Classifications
- CWE-284
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan cross-customer order-tampering proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo