Skip to main content
← Vulnerabilities

Bagisto before 2.3.16 and 2.4.x before 2.4.1 Race Condition in Coupon Usage Accounting

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.3MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 2.3.16, 2.4.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.3.16, 2.4.1.

38Pcve.now Index 38 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

CVE-2026-121628 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects bagisto; fixed in 2.3.16 and 2.4.1.

Published
Last modified
Published
Not listed in CISA KEV
38/100 · provisional
Fix
Fixed in 2.3.16, 2.4.1
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

Summary

Bagisto, an open-source e-commerce platform for Laravel, is affected by this flaw in its coupon handling during checkout. An attacker can send simultaneous order requests to apply a single-use discount coupon multiple times, resulting in unauthorized price reductions and lost revenue for store operators.

Read the original description

Bagisto before 2.3.16 and 2.4.x before 2.4.1 contains a race condition vulnerability in manageCartRule() that allows attackers to redeem single-use coupons multiple times. Attackers can submit concurrent order requests to the onepage orders checkout endpoint, bypassing unlocked times_used checks to apply discounts repeatedly.

What to do

  • Upgrade to a fixed version: 2.3.16, 2.4.1.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • bagisto bagisto

    fixed in 2.3.16; From 2.4.0 · fixed in 2.4.1

Evidence 8

  1. Patch
  2. Patch
  3. Exploit
  4. Repository
  5. Repository
Show all 8 sourcesShow fewer sources
  1. Repository
  2. Repository
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121628

Is CVE-2026-121628 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121628?

bagisto: before 2.3.16; from 2.4.0 before 2.4.1.Source: cve.now feed data

How do I fix CVE-2026-121628?

Upgrade to a fixed version: 2.3.16, 2.4.1.Source: cve.now feed data