Cyber Resilience

CVE-2025-62417

Webkul Bagisto 2.3.7

Public PoC
Published
16 October 2025
Modified
22 October 2025
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0037 29th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2025-62417 is a high-severity Improper Neutralization of Formula Elements in a CSV File (CWE-1236) vulnerability in Webkul Bagisto. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique User Execution (T1204); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-15 (Information Output Filtering) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Bagisto is an open source laravel eCommerce platform. When product data that begins with a spreadsheet formula character (for example =, +, -, or @) is accepted and later exported or saved into a CSV and opened in spreadsheet software,…

more

the spreadsheet will interpret that cell as a formula. This allows an attacker to supply a CSV field (e.g., product name) that contains a formula which may be evaluated by a victim’s spreadsheet application — potentially leading to data exfiltration and remote command execution (via older Excel exploits / OLE/cmd constructs or Excel macros). This vulnerability is fixed in 2.3.8.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1204 User Execution Execution
An adversary may rely upon specific actions by a user in order to gain execution.
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
T1566 Phishing Initial Access
Adversaries may send phishing messages to gain access to victim systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-60880Same product: Webkul Bagisto
CVE-2023-36236Same product: Webkul Bagisto
CVE-2023-33570Same product: Webkul Bagisto
CVE-2026-21449Same product: Webkul Bagisto
CVE-2023-36238Same product: Webkul Bagisto
CVE-2026-21447Same product: Webkul Bagisto
CVE-2026-21451Same product: Webkul Bagisto
CVE-2026-21446Same product: Webkul Bagisto
CVE-2025-62415Same product: Webkul Bagisto
CVE-2025-56426Same product: Webkul Bagisto

Affected Assets

webkul
bagisto
2.3.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10

Mitigating Controls (NIST 800-53 r5) AI

Output filtering/validation directly stops unneutralized formula elements from being written into CSV files.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require output neutralization for untrusted CSV content to block formula injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect formula injection but does not itself implement the mitigation.

prevents

Secure SDLC mandates input validation and output encoding that directly prevents formula injection in CSV exports.

prevents

Application security requirements include rules for safe CSV generation and handling of untrusted data.

prevents

Secure architecture principles encourage safe data export design but do not specifically address CSV formula neutralization.

prevents

Secure coding standards explicitly require neutralization of special characters when writing CSV files.

References