LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21450: Bagisto has SSTI in parameter that can lead to RCE

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.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Bagisto versions before 2.3.10 have a server-side template injection flaw in a type parameter. In the worst case, this can let an attacker run code on the server. The published CVSS data indicates exploitation requires high privileges, reducing broad internet risk but making compromise of admin-level accounts more serious.

Executive priority

Treat as high priority for any organization using Bagisto. The need for high privileges lowers mass-exploitation likelihood, but potential server code execution on an eCommerce platform creates meaningful business risk.

Technical view

CVE-2026-21450 is a CWE-1336 server-side template injection in Bagisto, an open source Laravel eCommerce platform. Affected versions are Bagisto before 2.3.10. The CVSS 4.0 vector is AV:N/AC:L/PR:H/UI:N with high confidentiality, integrity, and availability impact. Version 2.3.10 fixes the issue.

Likely exposure

Organizations running Bagisto versions earlier than 2.3.10 are exposed. Risk is highest where Bagisto is internet-accessible and high-privilege application accounts are shared, weakly protected, or compromised.

Exploitation context

The source bundle does not show known active exploitation, and KEV status is false. The advisory describes possible remote code execution, but CVSS indicates high privileges are required.

Researcher notes

Evidence is limited to the CVE record and GitHub advisory. No exploit details, affected endpoint path, or indicators of compromise are provided in the source bundle. Do not assume public exploitation without additional evidence.

Mitigation direction

  • Upgrade Bagisto to version 2.3.10 or later.
  • Review the GitHub security advisory for vendor-specific guidance.
  • Limit and monitor high-privilege Bagisto accounts until upgraded.
  • Prioritize MFA and strong credential hygiene for administrative users.

Validation and detection

  • Inventory Bagisto deployments and identify their installed versions.
  • Confirm no production instance is running below 2.3.10.
  • Verify upgrade completion through application release metadata.
  • Review privileged account activity for unusual administrative behavior.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1336: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21450 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (4.0)
Known Exploited
No
Published

Vector: CVSS: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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 4.0HighCVSS: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——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

7.3High
CVSS 4.0 vector shape for CVE-2026-21450Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS: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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
bagistobagisto< 2.3.10Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1336 · source CWE mapping

Improper Neutralization of Special Elements Used in a Template Engine

Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.