Order payment manipulation via unchecked orderId
Published Aug 29, 2026 · Updated Aug 29, 2026
Improper workflow enforcement in macrozheng mall 1.0.0 through 1.0.3 allows remote authenticated users to mark orders as paid. The /order/paySuccess controller accepts an attacker-selected orderId and payType, and paySuccess writes paid status, payment time, and pay type without checking order ownership, current status, or verified payment. Any mall member who can identify another order ID can alter that order and trigger stock updates, affecting order and inventory integrity.
Summary
What happened
Improper workflow enforcement in macrozheng mall 1.0.0 through 1.0.3 allows remote authenticated users to mark orders as paid. The /order/paySuccess controller accepts an attacker-selected orderId and payType, and paySuccess writes paid status, payment time, and pay type without checking order ownership, current status, or verified payment. Any mall member who can identify another order ID can alter that order and trigger stock updates, affecting order and inventory integrity.
The record
- CVE
- CVE-2026-82423
- Published
- Aug 29, 2026
- Updated
- Aug 29, 2026
- Vendor
- macrozheng
- Product
- mall
- Classifications
- CWE-840, CWE-841, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 29, 2026CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=1.0.0
- Affected versionversion=1.0.1
- Affected versionversion=1.0.2
- Affected versionversion=1.0.3
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.
Weakness, pattern, technique
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