Skip to main content
← Vulnerabilities

Bagisto before 2.4.5 Stored XSS via RMA Conversation Attachment Upload

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

2.1LowCNA
Exploited
No known exploitation
Fix
Fixed in 2.4.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.4.5.

5Pcve.now Index 5 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity2.1/10CVSS 2.1
  • No patch0/5No signal

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 24 if advisories confirm default setups are exposed

CVE-2026-121733 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.1 (low) and affects Bagisto; fixed in 2.4.5.

Published
Last modified
Published
Not listed in CISA KEV
5/100 · provisional
Fix
Fixed in 2.4.5
None on Exploit-DB, Metasploit or GitHub

Summary

Bagisto, an open-source Laravel-based e-commerce platform, is affected in versions before 2.4.5. An authenticated customer can upload an HTML file as a return (RMA) conversation attachment that runs malicious JavaScript in the store's web origin when an administrator opens it, potentially allowing session hijacking or actions taken on the admin's behalf.

Read the original description

Bagisto before 2.4.5 contains a stored cross-site scripting vulnerability that allows authenticated customers to upload HTML files via the RMA send-message endpoint without type or extension validation. Attackers can upload a .html attachment containing JavaScript served under /storage/rma-conversation/, executing script in the shop's origin when an administrator opens it.

What to do

  • Upgrade to a fixed version: 2.4.5.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Webkul Bagisto

    fixed in 2.4.5

Evidence 6

  1. Patch
  2. Patch
  3. Repository
  4. Repository
  5. Repository
  6. Link

Corrections

None so far.

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

FAQ

Questions about CVE-2026-121733

Is CVE-2026-121733 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. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121733?

Bagisto: before 2.4.5.Source: cve.now feed data

How do I fix CVE-2026-121733?

Upgrade to a fixed version: 2.4.5.Source: cve.now feed data