VulnerabilityPublished 17 Aug 2026

CVE-2026-75081: Webkul Bagisto · Enforcement of Behavioral Workflow

Affects Webkul BagistoSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: Proof of concept is public or traded
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-08-18.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by VulDB
17 Aug 202616:16 UTC, 7 hours before disclosure
CVE published
on cve.org
17 Aug 202623:45 UTC, t = 0
CISA SSVC assessment
proof of concept public
18 Aug 202613:31 UTC, 14 hours after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
WebkulBagisto	Affected 2.4.0 – 2.4.4 5 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:webkul:bagisto:*:*:*:*:*:*:*:*

AI-suggested

The vendor has already addressed some of the issues internally and plans to resolve remaining items in upcoming product releases. Users should monitor Webkul's official channels for updates and apply patches as they become available. Until official patches are released, no specific workaround or mitigation is provided by the vendor.

Description

CVE-2026-75081 is a medium severity vulnerability affecting Webkul Bagisto versions 2.4.0 through 2.4.4. It involves manipulation of parameters (rma_qty, resolution_type, rma_reason_id) in the /customer/account/rma/store endpoint, leading to enforcement of behavioral workflow. The vulnerability can be exploited remotely without user interaction. The vendor has acknowledged the issue and is addressing it through their internal security processes, with some fixes already implemented and others planned for future releases. Public exploit code is available, but no active exploitation in the wild has been reported.

Impact

The vulnerability allows remote attackers to manipulate certain parameters in the RMA (Return Merchandise Authorization) process, potentially altering the behavioral workflow of the application. This could lead to unauthorized actions or bypass of intended workflow controls. The CVSS 4.0 base score is 5.3 (medium), indicating a moderate impact with network attack vector, low attack complexity, no privileges required, no user interaction, and limited impact on confidentiality and integrity but some impact on availability or integrity via behavioral workflow enforcement.

Summary

This vulnerability in Webkul Bagisto up to version 2.4.4 allows remote attackers to manipulate specific arguments (rma_qty, resolution_type, rma_reason_id) in the /customer/account/rma/store file, resulting in enforcement of behavioral workflow. The exact nature of the behavioral workflow enforcement is not detailed, but the flaw is exploitable remotely without requiring user interaction or privileges beyond low-level privileges. The vendor has confirmed prior internal identification and partial remediation, with ongoing fixes planned. Public exploit code exists, increasing the risk of exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:14 UTC

Technical details

References

Community reviews

Related threats