Cyber Resilience

CVE-2026-21450

Webkul Bagisto ≤ 2.3.10

Published
02 January 2026
Modified
08 January 2026
Patch / advisory
CVSS Score v4 7.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/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.013 67th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2026-21450 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Webkul Bagisto. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-21450 is a server-side template injection vulnerability (CWE-1336) affecting Bagisto, an open source Laravel-based eCommerce platform. Versions prior to 2.3.10 are vulnerable through the "type" parameter, which enables attackers to inject malicious templates. The issue carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity due to its potential for high-impact exploitation.

The vulnerability can be exploited remotely over the network by unauthenticated attackers with low complexity and no user interaction required. Successful exploitation leads to remote code execution or other severe outcomes, such as full compromise of the affected server, granting high confidentiality, integrity, and availability impacts.

The official GitHub security advisory (GHSA-9hvg-qw5q-wqwp) confirms that upgrading to Bagisto version 2.3.10 resolves the issue by addressing the template injection flaw in the type parameter handling. Security practitioners should prioritize patching affected instances to mitigate risks.

EU & UK References

Vulnerability Data

Bagisto is an open source laravel eCommerce platform. Versions prior to 2.3.10 are vulnerable to server-side template injection via type parameter, which can lead to remote code execution or another exploitation. Version 2.3.10 fixes the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-21449Same product: Webkul Bagisto
CVE-2026-21448Same product: Webkul Bagisto
CVE-2025-62416Same product: Webkul Bagisto
CVE-2025-60880Same product: Webkul Bagisto
CVE-2023-36236Same product: Webkul Bagisto
CVE-2023-33570Same 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

Affected Assets

webkul
bagisto
≤ 2.3.10

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.3.2
  • V1.3.7
  • V1.3.10

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and static analysis can discover missing neutralization of template directives.

Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.

Security engineering principles require use of safe templating APIs and proper escaping of external input.

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 proper input neutralization in template engines to prevent 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 can detect template-injection flaws but does not itself implement neutralization controls.

prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

prevents

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References