Unauthorized withdrawal approval via state-changing GET request
Published Jul 14, 2026 · Updated Jul 14, 2026
Trusting HTTP permission methods in xianyu-auto-reply Server allows remote attackers to approve withdrawals via crafted GET requests. The withdrawal-review route changes approval state while handling GET, and its deterministic token derives from a record ID, action, and hard-coded secret. Network access and a guessed pending record ID are sufficient to compute the token and change a withdrawal from pending review to approved without administrator authentication.
Summary
What happened
Trusting HTTP permission methods in xianyu-auto-reply Server allows remote attackers to approve withdrawals via crafted GET requests. The withdrawal-review route changes approval state while handling GET, and its deterministic token derives from a record ID, action, and hard-coded secret. Network access and a guessed pending record ID are sufficient to compute the token and change a withdrawal from pending review to approved without administrator authentication.
The record
- CVE
- CVE-2026-15753
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- zhinianboke
- Product
- xianyu-auto-reply
- Classifications
- CWE-650, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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=n/a
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
- Withdrawal approval token and GET-request 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