dbcve.org
BagistoApplication · Webkul

CVE-2026-21448

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
Public exploit 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. When a normal customer orders any product, in the `add address` step they can inject a value to run in admin view. The issue can lead to remote code execution. Version 2.3.10 contains a patch.

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 before 2.3.10 suffer from a server-side template injection (SSTI) vulnerability in the checkout address input field. When a customer places an order and adds an address, malicious template syntax can be injected that executes when rendered in the admin dashboard view. This stems from improper sanitization of user input before it is passed to the Laravel Blade template engine, enabling remote code execution.

MitigationUpgrade to Bagisto version 2.3.10 or later which contains the patch. As an interim measure, input validation and output encoding should be applied to all address fields before rendering in admin views.

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 installed Bagisto version
    Check the composer.json file in the Bagisto root directory, or look for a version constant in config/app.php, or access the admin panel and check the system information page
    Affected if The version number is lower than 2.3.10
  2. Verify checkout address functionality exists
    Navigate to the storefront checkout page and confirm the address input fields are present and accessible to customers
    Affected if The checkout address form is enabled and functional (this is the default state)
  3. Inspect admin address rendering code
    Locate the admin view files that render customer addresses - typically in packages/Webkul/Admin/src/Resources/views/sales/addresses/ or similar paths. Check how address fields are passed to Blade templates
    Affected if The address data is rendered directly in Blade templates without using raw output escaping (e.g., {{ $address }} instead of {{ $address }} with sanitization, or the code uses {!! $address !!})
  4. Check address input sanitization in controller
    Examine the controller handling checkout address submission (typically in packages/Webkul/Checkout/src/Http/Controllers). Look for input validation or sanitization before the address is saved to the database
    Affected if There is no input validation or sanitization applied to address fields before database storage, or sanitization is missing specific template syntax filtering
  5. Test address field for SSTI in admin view
    Place a test order with a crafted address containing template syntax (e.g., {{ 7*7 }}). Then view this address in the admin panel. If the result renders as 49 instead of the literal string, the vulnerability is present
    Affected if The expression evaluates and displays 49 in the admin dashboard, confirming template injection is possible

You are affected if your Bagisto installation is version 2.3.10 or lower and the checkout address fields render directly in admin views without proper input sanitization or output encoding.

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 patch. As an interim measure, input validation and output encoding should be applied to all address fields before rendering in admin views.

Recommended fix Moderate confidence

2.3.10

  1. Backup the current Bagisto installation and database before proceeding
  2. Confirm the current version is below 2.3.10 by checking composer.json or the admin panel
  3. Upgrade Bagisto to version 2.3.10 using composer update (e.g., composer update bagisto/bagisto:2.3.10 or by updating the version constraint in composer.json)
  4. Clear cached files (php artisan cache:clear, php artisan config:clear)
  5. Verify the upgrade was successful by checking the version in the admin panel
  6. Test that the address functionality works correctly in both customer and admin views

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

Fix this in Bagisto Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21448 — 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-21448 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