/

CVE-2026-21446

Severity:

CRITICAL RISK

(9.8)

Missing Authentication / Authorization in Bagisto eCommerce

CVE-2026-21446

Analyzed

Vulnerability type

Category:

Missing Authentication / Authorization

CWE:

CWE-306

Impact:

Unauthenticated Admin Account Creation and Full Application Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Bagisto's installer API endpoints remain exposed and unauthenticated after setup in affected 2.3.x versions, allowing direct access to /install/api/*.

An attacker can abuse these endpoints without logging in to create admin accounts, change application settings, and overwrite existing data in a deployed store.

Affected context

This vulnerability appears in Bagisto deployments on the 2.3 branch prior to 2.3.10 where the installation API routes are not disabled or protected after the initial setup completes.

The issue is specific to the installer component's API endpoints under /install/api/*, which remain routable and functional in production environments.

It is most critical for internet-exposed Bagisto stores where network access to these routes is possible from untrusted clients.

Exploit preconditions

  • Attack surface: Public-facing web application, specifically HTTP(S) requests to /install/api/*.
  • Required access: Network access to the Bagisto instance; no prior authentication or valid user account is required.
  • Trigger point: Direct invocation of installer API endpoints after the application has already been installed.
  • Why exploitation is possible: The installer API routes are left enabled and do not enforce any authentication or post-installation lock, allowing arbitrary calls to privileged installation functionality.

Why this happens

The core issue is a failure to enforce authentication and lifecycle restrictions on sensitive installer endpoints.

After installation, high-privilege operations exposed via /install/api/* remain accessible without verifying that the caller is an authenticated and authorized user or that the installer should be disabled.

This maps to CWE-306: Missing Authentication for Critical Function, where functions that can create administrator accounts and alter core configuration are exposed without any authentication gate.

Architecturally, the installer behaves as if the application is still in setup mode, instead of transitioning to a locked-down production mode after successful installation.

Potential impact

  • An attacker can create new administrator accounts with full control over the eCommerce platform.
  • An attacker can modify critical application configurations (payment, shipping, email, store settings).
  • Existing data, including products, orders, or configuration, can be overwritten or tampered with.
  • Complete compromise of the storefront, including defacement and operational disruption.
  • Indirect impact on customers, such as fraudulent orders or exposure of sensitive operational data.

General mitigation guidance

Effective mitigation focuses on securing or eliminating post-installation access to privileged installer functionality.

Common defensive patterns include:

  • Ensuring installer and setup routes are disabled or removed automatically after successful installation.
  • Placing installer endpoints behind strict authentication and authorization checks, even during installation, with explicit teardown logic afterward.
  • Using environment-based flags (e.g., "INSTALLED" or maintenance modes) to conditionally register or block installation routes at runtime.
  • Segregating installation logic from the main application and deploying installer code only in controlled, temporary environments.
  • Minimizing privileges of web-facing components so that even if an installer endpoint is exposed, its ability to modify core configuration and accounts is constrained.

How teams detect issues like this

Detection typically combines configuration review and behavioral monitoring:

  • Static analysis / code review: Look for route registrations for installation or setup paths (e.g., /install, /setup) that are always enabled regardless of application state or environment.
  • Access control review: Verify that any high-privilege routes (account creation, configuration changes) enforce authentication, role checks, and installation-state checks.
  • Runtime monitoring: Inspect web access logs for suspicious unauthenticated requests to /install/api/* paths in production environments.
  • Security testing: Include checks in integration or penetration tests to probe for accessible installation, upgrade, or maintenance endpoints after deployment.
  • Automated code scanning or policy-as-code tools can flag patterns where critical functions are reachable without authentication guards.

Sources

SourceLink
github.comgithub.com/bagisto/bagisto/commit/380c045e48490da740cd505fb192cc45e1809bed
github.comgithub.com/bagisto/bagisto/security/advisories/GHSA-6h7w-v2xr-mqvw

Frequently asked

questions

Yes. If the Bagisto instance is reachable over the network and the /install/api/* routes are accessible, an attacker can exploit the vulnerability remotely without prior access.

No credentials are required. The affected installer API endpoints do not enforce authentication, so any unauthenticated user with network access can send requests to them.

The safest pattern is to completely disable or remove installer routes and logic once installation is finished, and ensure any remaining setup-related functionality is protected by strong authentication and authorization checks tied to the application's runtime state.

Treat installers, setup wizards, and maintenance panels as highly privileged components: design them to be time-limited, state-aware, and disabled by default in production; enforce strict authentication on all critical operations; and include explicit checks for installation state in route registration and controller logic.

Find out what's already
exploitable in your codebase.