Workflow integrity bypass via unchecked RMA fields
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 write invalid RMA records via crafted parameters. The /customer/account/rma/store handler validates only that rma_qty, resolution_type, and rma_reason_id are present, then writes those attacker-controlled values into the RMA item record without rechecking server-side quantity limits, allowed resolution states, or reason-to-resolution bindings. Exploitation requires a normal customer account with access to RMA creation, and the documented impact is integrity-only: excessive quantities and unsupported resolution or reason combinations can corrupt after-sales workflow data and misroute later refund or cancellation handling.
Summary
What happened
Business-logic bypass in Webkul Bagisto 2.4.0 through 2.4.4 allows remote authenticated users to write invalid RMA records via crafted parameters. The /customer/account/rma/store handler validates only that rma_qty, resolution_type, and rma_reason_id are present, then writes those attacker-controlled values into the RMA item record without rechecking server-side quantity limits, allowed resolution states, or reason-to-resolution bindings. Exploitation requires a normal customer account with access to RMA creation, and the documented impact is integrity-only: excessive quantities and unsupported resolution or reason combinations can corrupt after-sales workflow data and misroute later refund or cancellation handling.
The record
- CVE
- CVE-2026-75081
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- Bagisto
- Product
- Bagisto
- Classifications
- CWE-841, CWE-840, 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 RMA workflow validation 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