Order payment forgery via unchecked order identifier
Published Sep 15, 2025 · Updated Sep 15, 2025
Improper authorization in newbee-mall allows remote authenticated users to mark arbitrary orders as paid through /paySuccess. The paySuccess controller accepts a client-supplied orderNo, retrieves that order, and writes paid status and payment details without verifying ownership or a trusted payment callback. A normal authenticated account and another order number are sufficient to alter that order's payment state, enabling zero-cost purchases.
Summary
What happened
Improper authorization in newbee-mall allows remote authenticated users to mark arbitrary orders as paid through /paySuccess. The paySuccess controller accepts a client-supplied orderNo, retrieves that order, and writes paid status and payment details without verifying ownership or a trusted payment callback. A normal authenticated account and another order number are sufficient to alter that order's payment state, enabling zero-cost purchases.
The record
- CVE
- CVE-2025-10422
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- newbee-ltd
- Product
- newbee-mall
- Classifications
- CWE-266, CWE-285, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=613a662adf1da7623ec34459bc83e3c1b12d8ce7
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.
Weakness, pattern, technique
Public exploit references
- Authenticated /paySuccess order-status proof of conceptfunctional · 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