Webkul Bagisto up to 2.4.4 store rma_qty/resolution_type/rma_reason_id behavioral workflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.21+ |
Summary
A vulnerability identified as problematic has been detected in Webkul Bagisto up to 2.4.4. The affected element is an unknown function of the file /customer/account/rma/store. This manipulation of the argument rma_qty/resolution_type/rma_reason_id causes behavioral workflow. The identification of this vulnerability is CVE-2026-75081. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The vendor confirms: "The reported issues were already identified through our internal security assessment process prior to this notification and are being handled through our established internal security and development lifecycle. Some of these items have already been addressed, while the remaining items are planned for resolution in upcoming product releases."
Details
A vulnerability was found in Webkul Bagisto up to 2.4.4. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the file /customer/account/rma/store. The manipulation of the argument rma_qty/resolution_type/rma_reason_id with an unknown input leads to a behavioral workflow vulnerability. The CWE definition for the vulnerability is CWE-841. The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence. As an impact it is known to affect integrity.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-75081. The exploitation appears to be easy. The attack can be launched remotely. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vendor confirms: "The reported issues were already identified through our internal security assessment process prior to this notification and are being handled through our established internal security and development lifecycle. Some of these items have already been addressed, while the remaining items are planned for resolution in upcoming product releases."
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Behavioral workflowCWE: CWE-841 / CWE-840
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/17/2026 Advisory disclosed08/17/2026 VulDB entry created
08/17/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2026-75081 (🔒)
GCVE (CVE): GCVE-0-2026-75081
GCVE (VulDB): GCVE-100-391309
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/17/2026 18:21Changes: 08/17/2026 18:21 (56)
Complete: 🔍
Submitter: Mitch_45
Cache ID: 216::103
Submit
Accepted
- Submit #870359: Webkul Bagisto <=2.4.4 Improper Input Validation (by Mitch_45)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.