Unauthenticated order-status modification via unchecked callback
Published Jul 11, 2024 · Updated Apr 8, 2026
Missing authorization in Payflex Payment Gateway 2.5.0 and earlier allows remote attackers to alter WooCommerce order statuses. The payment_callback() handler trusted callback-supplied status data instead of confirming the order status through Payflex's remote API. An internet-reachable store with the gateway enabled exposes the callback, allowing forged data to alter an order's recorded payment state and cause revenue loss.
Summary
What happened
Missing authorization in Payflex Payment Gateway 2.5.0 and earlier allows remote attackers to alter WooCommerce order statuses. The payment_callback() handler trusted callback-supplied status data instead of confirming the order status through Payflex's remote API. An internet-reachable store with the gateway enabled exposes the callback, allowing forged data to alter an order's recorded payment state and cause revenue loss.
The record
- CVE
- CVE-2024-0619
- Published
- Jul 11, 2024
- Updated
- Apr 8, 2026
- Vendor
- Payflex
- Product
- Payflex Payment Gateway
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 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.5.0
- Affected versionversion=2.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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