dbcve.org
BagistoApplication · Webkul

CVE-2026-21446

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 Patch available

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. In versions on the 2.3 branch prior to 2.3.10, API routes remain active even after initial installation is complete. The underlying API endpoints (`/install/api/*`) are directly accessible and exploitable without any authentication. An attacker can bypass the Ib installer entirely by calling the API endpoints directly. This allows any unauthenticated attacker to create admin accounts, modify application configurations, and potentially overwrite existing data. 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 have installer API endpoints (/install/api/*) that remain accessible after initial installation completes without any authentication. This allows unauthenticated attackers to directly call these APIs to create admin accounts, modify application configurations, and potentially overwrite existing data.

MitigationUpgrade to Bagisto version 2.3.10 or later which disables the installer API routes after installation. If immediate patching is not possible, block external access to /install/api/* routes at the web server or firewall level.

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.0, < 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 and version
    Locate the Bagisto installation directory and check the version. In the root directory, examine the composer.json file for the 'version' field, or check any version configuration file. Alternatively, check the composer.lock file for the bagisto package version.
    Affected if The installed version is >= 2.3.0 and < 2.3.10 (check the exact version string in composer.json or composer.lock)
  2. Verify the installer directory still exists
    Check if the /install directory and its subdirectories (including /install/api) still exist in the web root. List the contents of the install directory if it is present.
    Affected if The /install/api directory exists in the web root after installation is complete
  3. Test access to installer API endpoints
    Send an HTTP request to the /install/api/* endpoints. For example, use curl or a browser to access http://your-domain/install/api/ or test an endpoint like /install/api/configuration. No authentication should be required for this test if the vulnerability exists.
    Affected if The /install/api routes respond with HTTP 200 or other successful status codes without requiring any authentication
  4. Check for newly created admin accounts
    Review the admin user table in the database or the admin users configuration to identify any admin accounts that were not created by legitimate administrators. Check for unexpected admin users with suspicious email addresses or usernames.
    Affected if There are admin accounts in the system that were not created by known, authorized administrators

You are affected if your Bagisto version is 2.3.0 through 2.3.9 and the /install/api/* routes are accessible without authentication after installation has completed.

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
Vendor patch github.com →
Interim mitigation

Upgrade to Bagisto version 2.3.10 or later which disables the installer API routes after installation. If immediate patching is not possible, block external access to /install/api/* routes at the web server or firewall level.

Recommended fix High confidence

Bagisto 2.3.10

  1. Backup the entire Bagisto installation including database and files
  2. Update composer.json to require bagisto/bagisto version 2.3.10 (e.g., composer require bagisto/bagisto:2.3.10 --no-update)
  3. Run composer update to install the fixed version
  4. Alternatively, apply the vendor patch from commit 380c045e48490da740cd505fb192cc45e1809bed if staying on current minor version
  5. Run php artisan migrate if any database changes are included in the update
  6. Clear application cache: php artisan cache:clear
  7. Clear compiled views: php artisan view:clear
  8. Verify the /install/api/* routes are no longer accessible without authentication
Caveat Minor version upgrade in the same 2.x branch typically has minimal breaking changes; review release notes for any configuration changes

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

Fix this in Bagisto Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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