Skip to main content
VulnerabilityPublished

CVE-2026-19996: Webkul Bagisto · CWE-266

Source GCVE Database

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

Public exploit available · CVSS 5.3 Medium.

Data as of 16 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 32% 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:L/VI:N/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

    , 13 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 32 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 16 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 already addressed some of the issues internally and plans to resolve the remaining items in upcoming product releases. Users should monitor vendor communications for updates and apply patches once available. Until then, restricting access to the affected endpoint and ensuring least privilege principles may help reduce risk.

Description

A vulnerability in Webkul Bagisto up to version 2.4.4 affects the Backend Customer Behavior Data Endpoint at /admin/customers. The flaw involves improper privilege management due to manipulation of the ID argument. The vulnerability can be exploited remotely and public exploit code is available. 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.

References

Community reviews

Loading reviews…