Payment bypass via unbound order identifiers
Published May 24, 2025 · Updated May 28, 2025
Business-logic flaw in Tmall Demo 20250505 allows remote attackers to bypass payment by substituting another order identifier. The /tmall/order/pay/ workflow accepts attacker-supplied order identifiers across its success and confirmation requests without binding them to the original transaction. Unauthenticated exploitation requires a specific two-request sequence and can remove an item from the cart while leaving the order pending without valid payment.
Summary
What happened
Business-logic flaw in Tmall Demo 20250505 allows remote attackers to bypass payment by substituting another order identifier. The /tmall/order/pay/ workflow accepts attacker-supplied order identifiers across its success and confirmation requests without binding them to the original transaction. Unauthenticated exploitation requires a specific two-request sequence and can remove an item from the cart while leaving the order pending without valid payment.
The record
- CVE
- CVE-2025-5136
- Published
- May 24, 2025
- Updated
- May 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, CWE-310, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2025CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Tmall Demo payment-workflow 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