Workflow bypass via unchecked RMA status update
Published Aug 17, 2026 · Updated Aug 18, 2026
Business logic bypass in Webkul Bagisto 2.4.0 through 2.4.4 allows remote authenticated users to alter RMA status via POST requests. The customer updateStatus handler behind /customer/account/rma/update-status/{id} accepts close_rma and writes SOLVED after checking only record ownership, without revalidating whether the current RMA state is closeable. Reachability requires a normal customer session and an RMA tied to that account; the result is unauthorized workflow-state changes such as forcing DECLINED requests to SOLVED and disrupting return-processing records.
Summary
What happened
Business logic bypass in Webkul Bagisto 2.4.0 through 2.4.4 allows remote authenticated users to alter RMA status via POST requests. The customer updateStatus handler behind /customer/account/rma/update-status/{id} accepts close_rma and writes SOLVED after checking only record ownership, without revalidating whether the current RMA state is closeable. Reachability requires a normal customer session and an RMA tied to that account; the result is unauthorized workflow-state changes such as forcing DECLINED requests to SOLVED and disrupting return-processing records.
The record
- CVE
- CVE-2026-19993
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- Bagisto
- Product
- Bagisto
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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=2.4.0
- Affected versionversion=2.4.1
- Affected versionversion=2.4.2
- Affected versionversion=2.4.3
- Affected versionversion=2.4.4
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
- Bagisto force-close issue reproduction reportproof 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