Skip to main content
VulnerabilityPublished

CVE-2026-75081: Webkul Bagisto

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-75081· Medium 5.3

Public exploit available · CVSS 5.3 Medium.

Data as of 15 Nov 2026, 20:25 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 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

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

  1. Disclosed: evidence found.

    CVE published 17 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulDB

    , 7 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 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 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
WebkulBagistoAffected
  • 2.4.0 – 2.4.4
5 affected builds
Fixed in–

AI-suggested

The vendor has confirmed that some issues related to this vulnerability have already been fixed, and the remaining are planned for resolution in upcoming releases. Users should apply updates as they become available from the vendor. Until patches are released, monitoring vendor advisories for official fixes is recommended. No specific temporary mitigations are provided by the vendor.

Description

A vulnerability exists in Webkul Bagisto versions up to 2.4.4 affecting an unknown function in the /customer/account/rma/store file. The flaw involves manipulation of the rma_qty, resolution_type, or rma_reason_id arguments, which can enforce unintended behavioral workflow changes. The vulnerability can be exploited remotely. The vendor has acknowledged the issue, stating that some fixes have already been implemented and remaining issues are planned to be resolved in upcoming releases. The CVSS score is 4.3, indicating a medium severity level.

References

Community reviews

Loading reviews…