提交 #870354: Webkul Bagisto <=2.4.4 Business Logic Errors

Bagisto 2.4.4 contains server-side RMA state validation bypasses in frontend customer RMA operations. A normal authenticated customer can directly send state-changing requests and force invalid RMA state transitions that the frontend no longer allows.

Affected endpoints include POST /customer/account/rma/update-status/{id} and POST /customer/account/rma/cancel/{id}. The frontend computes whether actions such as closing or canceling an RMA should be available, but the backend does not fully enforce the same state-transition rules. For example, a customer can directly submit a status update request and force an RMA from DECLINED to SOLVED even when the close action is not visible in the UI. A related case allows direct cancellation of an already solved RMA because the backend checks ownership and whether the request is already canceled, but does not enforce a complete cancelable-state decision.

The impact is unauthorized manipulation of the RMA lifecycle by the owning customer. This can prematurely terminate after-sales workflows, overwrite processed states, confuse support staff, and introduce incorrect status data into notifications, reporting, and audit trails. The issue is a business logic flaw caused by relying on frontend action visibility instead of enforcing state-transition rules on the server.

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/37_38_english_vulnerability_report.md
• 用户: Mitch45 (UID 99299)
• 提交: 2026-06-26 06時44分 (2 月前)
• 管理: 2026-08-16 20時05分 (2 months later)
• 状态: 已接受
• VulDB条目: 391194 [Webkul Bagisto 直到 2.4.4 RMA State Validation update-status 权限提升]
• 积分: 20