CVE-2025-56426: n/a
Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
Immediate mitigation steps include restricting access to the Cart/Checkout API endpoint through network segmentation and firewall rules to limit exposure to trusted IPs only. Organizations should implement strict input validation and sanitization on quantity parameters at the application level as a temporary control. Monitoring API logs for anomalous or unexpected quantity values can help detect exploitation attempts early. It is critical to apply official patches from WebKul as soon as they become available. In the interim, consider deploying Web Application Firewalls (WAFs) with custom rules to block suspicious payloads targeting the quantity input fields. Conduct thorough code reviews and penetration testing focused on the checkout process to identify similar logic flaws. Additionally, ensure that backup and incident response plans are updated to address potential breaches stemming from this vulnerability.
Description
An issue WebKul Bagisto v.2.3.6 allows a remote attacker to execute arbitrary code via the Cart/Checkout API endpoint, specifically, the price calculation logic fails to validate quantity inputs properly.