MEDIUMCVE-2025-62415CVSS 6.9

CVE-2025-62415: XSS in Bagisto eCommerce Platform

Platform

laravel

Component

bagisto/bagisto

Fixed in

2.3.8

CVE-2025-62415 is a cross-site scripting (XSS) vulnerability discovered in Bagisto, an open-source Laravel eCommerce platform. This flaw allows authenticated attackers, such as administrators, to inject malicious HTML and JavaScript code through the TinyMCE image upload functionality. Successful exploitation can lead to session hijacking, data theft, and defacement of the eCommerce site. The vulnerability impacts versions of Bagisto up to 2.3.8, and a patch is available in version 2.3.8.

PHP / Composer

Detect this CVE in your project

Upload your composer.lock file and we'll tell you instantly if you're affected.

Impact and Attack Scenarios

The primary impact of CVE-2025-62415 is the potential for an attacker to execute arbitrary JavaScript code within the context of a user's browser, specifically targeting administrators or other users with sufficient privileges. This can be leveraged to steal session cookies, allowing the attacker to impersonate the user and gain unauthorized access to sensitive data and functionalities within the Bagisto eCommerce platform. An attacker could also inject malicious scripts to redirect users to phishing sites, display deceptive content, or modify the appearance of the website to trick users into divulging information. The blast radius extends to any user who views the content containing the injected script, potentially compromising the entire user base.

Exploitation Context

CVE-2025-62415 has a Medium exploitation probability based on the requirement of authenticated access. No public proof-of-concept (POC) code has been publicly released as of the publication date. The vulnerability was published on 2025-10-16. It is not currently listed on KEV or EPSS, suggesting a low level of immediate threat. Monitor security advisories and threat intelligence feeds for any indications of active exploitation.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh

EPSS

0.03% (8% percentile)

CISA SSVC

Exploitationpoc
Automatableno
Technical Impactpartial

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N6.9MEDIUMAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredHighAuthentication level needed to attackUser InteractionRequiredWhether a victim must take actionScopeChangedImpact beyond the vulnerable componentConfidentialityHighRisk of sensitive data exposureIntegrityLowRisk of unauthorized data modificationAvailabilityNoneRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
High — admin or privileged account required to exploit.
User Interaction
Required — victim must take an action: open a file, click a link, or visit a crafted page.
Scope
Changed — successful attack can pivot beyond the vulnerable component to other systems or the host OS.
Confidentiality
High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
Integrity
Low — attacker can modify some data with limited scope or impact.
Availability
None — no availability impact. Service remains fully operational.

Affected Software

Componentbagisto/bagisto
Vendorbagisto
Maximum version< 2.3.8
Fixed in2.3.8

Weakness Classification (CWE)

Timeline

  1. Reserved
  2. Published
  3. Modified
  4. EPSS updated

Mitigation and Workarounds

The recommended mitigation for CVE-2025-62415 is to immediately upgrade Bagisto to version 2.3.8 or later, which contains the fix for this vulnerability. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) rule to block uploads of HTML files containing JavaScript code. Additionally, carefully review and sanitize all user-generated content before displaying it on the website. Regularly audit user roles and permissions to ensure that only authorized personnel have access to administrative functionalities. After upgrading, confirm the fix by attempting to upload a test HTML file containing a simple JavaScript alert and verifying that the alert does not execute.

How to fix

Actualice Bagisto a la versión 2.3.8 o superior. Esta versión corrige la vulnerabilidad XSS en la funcionalidad de carga de imágenes de TinyMCE. La actualización evitará que atacantes ejecuten código JavaScript malicioso en el contexto del navegador de los administradores.

Frequently asked questions

What is CVE-2025-62415 — XSS in Bagisto eCommerce Platform?

CVE-2025-62415 is a cross-site scripting (XSS) vulnerability affecting Bagisto versions up to 2.3.8. It allows authenticated attackers to upload malicious HTML files via TinyMCE, potentially executing JavaScript in a user's browser.

Am I affected by CVE-2025-62415 in Bagisto eCommerce Platform?

You are affected if you are running Bagisto version 2.3.8 or earlier. Verify your version and upgrade immediately to mitigate the risk.

How do I fix CVE-2025-62415 in Bagisto eCommerce Platform?

Upgrade Bagisto to version 2.3.8 or later. As a temporary workaround, implement a WAF rule to block HTML file uploads containing JavaScript.

Is CVE-2025-62415 being actively exploited?

As of the publication date, there are no public reports of active exploitation. However, it's crucial to apply the patch promptly to prevent potential future attacks.

Where can I find the official Bagisto advisory for CVE-2025-62415?

Refer to the official Bagisto security advisories and release notes on the Bagisto website or GitHub repository for the latest information and updates regarding CVE-2025-62415.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

PHP / Composer

Detect this CVE in your project

Upload your composer.lock file and we'll tell you instantly if you're affected.

livefree scan

Scan your PHP / Composer project now — no account

Upload your composer.lock and get the vulnerability report instantly. No account. Uploading the file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...