dbcve.org
BagistoApplication · Webkul

CVE-2026-21450

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-02
Fix available
A fix is available. Upgrade to 2.3.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Bagisto versions prior to 2.3.10 contain a server-side template injection (SSTI) vulnerability in the type parameter. This allows attackers to inject malicious template code that is executed server-side, leading to remote code execution.

MitigationUpgrade to Bagisto version 2.3.10 or later, which contains the fix for this SSTI vulnerability. If immediate upgrading is not possible, restrict access to affected endpoints and implement input validation on the type parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BagistoApplication
Affected:< 2.3.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Bagisto installation path
    Locate the Bagisto installation directory on your web server, typically found in the web root (e.g., /var/www/html/bagisto or similar).
    Affected if The installation directory exists and contains Bagisto files.
  2. Find the installed Bagisto version
    Check the composer.json file in the Bagisto root directory for the 'version' field, or look for a VERSION file in the application root.
    Affected if The version field shows a version lower than 2.3.10 (e.g., 2.3.0, 2.2.0, etc.) or no version is specified.
  3. Verify the vulnerable endpoint is accessible
    Check if routes accepting a 'type' parameter are publicly accessible. Common areas include template-related routes, export functionality, or any Blade template rendering that uses user input.
    Affected if The application processes the 'type' parameter without sanitization in template rendering contexts.
  4. Inspect request handling for the type parameter
    Review application logs and network traffic for requests containing a 'type' parameter that gets passed to template rendering functions (e.g., Blade::render, view())->
    Affected if Requests with a 'type' parameter reach template rendering logic without input validation.
  5. Check for signs of successful exploitation
    Examine server logs, web access logs, and the application for unexpected file creation, command execution artifacts, or modified files indicating code execution.
    Affected if Suspicious files in the application directory, unexpected processes, or log entries showing template injection payloads.

You are affected if your Bagisto installation version is lower than 2.3.10 and the application exposes endpoints that accept a 'type' parameter for template rendering without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.10 or later
Fixed in 2.3.10
Interim mitigation

Upgrade to Bagisto version 2.3.10 or later, which contains the fix for this SSTI vulnerability. If immediate upgrading is not possible, restrict access to affected endpoints and implement input validation on the type parameter.

Recommended fix High confidence

2.3.10

  1. Backup your Bagisto installation including the database and all files
  2. Update your composer.json to require bagisto version 2.3.10 or higher, or run 'composer update bagisto/bagisto' to fetch the latest version
  3. Run 'composer install' or 'composer update' to apply the changes
  4. Run database migrations if any are required: 'php artisan migrate'
  5. Clear the application cache: 'php artisan cache:clear' and 'php artisan config:clear'
  6. Clear view cache: 'php artisan view:clear'
  7. Verify the upgrade was successful by checking the Bagisto version in the admin panel or via CLI
Caveat Review release notes for 2.3.10 to check for any breaking changes or required configuration updates before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bagisto Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21450 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data