LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21449: Bagisto has SSTI via first and last name from low-privilege user (not admin)

Bagisto is an open source laravel eCommerce platform. Versions prior to 2.3.10 are vulnerable to server-side template injection via first name and last name from a low-privilege user. Version 2.3.10 fixes the issue.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Bagisto eCommerce sites before version 2.3.10 have a high-severity flaw where a low-privilege user’s first or last name can trigger server-side template injection. In practical terms, a registered customer account may be enough to affect the server-side application. Bagisto 2.3.10 fixes the issue.

Executive priority

Treat as a high-priority eCommerce platform update. The issue may be reachable by low-privilege users and can affect server confidentiality, integrity, and availability. Upgrade exposed Bagisto stores promptly, with highest priority for public sites allowing customer accounts.

Technical view

CVE-2026-21449 is CWE-1336 server-side template injection in Bagisto before 2.3.10. The CVSS 4.0 score is 7.4 high: network-reachable, low complexity, low privileges required, no user interaction, with high confidentiality, integrity, and availability impact to the vulnerable system.

Likely exposure

Public Bagisto storefronts below 2.3.10 are most exposed, especially where untrusted users can create accounts or edit profile names. The source identifies first name and last name fields as the injection path. Admin privilege is not required.

Exploitation context

The record is not in CISA KEV, and the provided sources do not state active exploitation. The CVSS vector includes exploit maturity “P,” indicating proof-of-concept maturity in the scoring data, but no exploit details are provided here.

Researcher notes

Evidence is limited to the CVE data and Bagisto advisory reference. The core issue is SSTI through first and last name values in versions before 2.3.10. No active exploitation claim is supported by the provided sources, and no weaponization details should be inferred.

Mitigation direction

  • Upgrade Bagisto to version 2.3.10 or later.
  • Review the GitHub security advisory for vendor-specific guidance.
  • Prioritize internet-facing stores with customer registration enabled.
  • If immediate upgrade is delayed, reduce untrusted profile-name changes where operationally feasible.

Validation and detection

  • Inventory all Bagisto deployments and record running versions.
  • Confirm each deployment is version 2.3.10 or later.
  • Review whether customer registration or profile editing is enabled.
  • Check application logs for unusual activity involving name/profile fields.
  • Track remediation status for all public storefronts.
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
cve · low confidence lookup

CVE-2026-21449 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.4 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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.4CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/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.4High
CVSS 4.0 vector shape for CVE-2026-21449Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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.