| 标题 | Webkul Bagisto <=2.4.4 Improper Input Validation |
|---|
| 描述 | Bagisto 2.4.4 contains multiple server-side business validation bypasses in frontend RMA creation. A normal authenticated customer can modify request parameters and create RMA records that violate quantity, resolution, and reason constraints enforced by the user interface.
The affected endpoint is POST /customer/account/rma/store. The frontend limits fields such as rma_qty, resolution_type, and rma_reason_id, but the backend validation checks mainly that the fields are present and then persists attacker-controlled values. A customer can intercept the RMA creation request and submit an excessive rma_qty beyond the allowed quantity, forge a resolution_type that the UI does not allow for the order item, or submit an rma_reason_id that does not belong to the chosen resolution_type.
The impact is unauthorized manipulation of the after-sales workflow and RMA data integrity. A customer can create RMA records with excessive quantities, unsupported resolution types, or inconsistent reason mappings. These manipulated records may mislead customer-service staff, pollute operational records, and affect later cancellation, return, refund, or reporting workflows. The issue is a server-side business logic and input validation failure because the server relies on UI restrictions instead of revalidating the rules before storing the RMA.
The vendor was contacted beforehand and confirmed the report. No CVE is included in the public report at the time of preparation.
|
|---|
| 来源 | ⚠️ https://github.com/Mitchell45/PHP_Web_POCs/blob/main/Bagisto/34_36_english_vulnerability_report.md |
|---|
| 用户 | Mitch_45 (UID 99298) |
|---|
| 提交 | 2026-06-26 06時49分 (4 月前) |
|---|
| 管理 | 2026-08-17 18時16分 (2 months later) |
|---|
| 状态 | 已接受 |
|---|
| VulDB条目 | 391309 [Webkul Bagisto 直到 2.4.4 store rma_qty/resolution_type/rma_reason_id 权限提升] |
|---|
| 积分 | 20 |
|---|