Unauthenticated order-status changes via missing capability check
Published Mar 13, 2024 · Updated Apr 8, 2026
Improper access control in Duitku Payment Gateway 2.11.6 and earlier allows remote attackers to mark WooCommerce orders as failed. The check_duitku_response function updates the targeted order's payment status without checking the caller's capabilities. No account or user interaction is required; successful exploitation forces the failed state rather than exposing payment data.
Summary
What happened
Improper access control in Duitku Payment Gateway 2.11.6 and earlier allows remote attackers to mark WooCommerce orders as failed. The check_duitku_response function updates the targeted order's payment status without checking the caller's capabilities. No account or user interaction is required; successful exploitation forces the failed state rather than exposing payment data.
The record
- CVE
- CVE-2024-0631
- Published
- Mar 13, 2024
- Updated
- Apr 8, 2026
- Vendor
- Duitku
- Product
- Duitku Payment Gateway
- Classifications
- CWE-284, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 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.11.6
What conditions does exploitation require?
What is affected?
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.
Public exploit references
No public exploit references are available in this record.
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