/

CVE-2026-79410

Severity:

HIGH RISK

(8.1)

Improper Input Validation (CWE-20) in Bagisto Cart Path

CVE-2026-79410

Deferred

Vulnerability type

Category:

Improper Input Validation

CWE:

CWE-20

Impact:

Price Manipulation and Financial Loss

Severity:

HIGH RISK

(8.1)

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

Webkul Bagisto v2.4.9 improperly validates the quantity parameter in its add-to-cart workflow. An authenticated attacker may manipulate this value to reduce the calculated order total below the legitimate price of shippable goods, creating a risk of financial loss and order-integrity failures.

Affected context

The vulnerability occurs in Bagisto's add-to-cart path when quantity input is accepted without sufficiently enforcing the expected value range and business rules. It becomes risky in deployments where authenticated users can submit crafted cart requests and the resulting quantity is used in pricing or order calculations without consistent server-side validation.

Exploit preconditions

  • Attack surface: The authenticated add-to-cart application endpoint
  • Required access: A valid user account capable of adding products to a cart
  • Trigger point: Processing of the quantity parameter during cart creation or update
  • Why exploitation is possible: Insufficient validation allows unexpected quantity values to influence order pricing and total calculations

Why this happens

The underlying bug is improper input validation, mapped to CWE-20. The application accepts a quantity value without reliably checking its type, range, and relationship to the product and order rules before using it in cart and price calculations. This insecure pattern allows client-controlled input to affect trusted business logic.

Potential impact

  • An attacker may obtain shippable goods at an incorrectly reduced price
  • The application could record inaccurate cart and order totals
  • Merchants may experience financial losses
  • Inventory and fulfillment records may become inconsistent
  • The issue could undermine trust in pricing and checkout controls

General mitigation guidance

Mitigation generally focuses on treating quantity as untrusted input and enforcing business rules on the server side.

Common defensive patterns include:

  • Accepting only the intended numeric type and a strictly bounded positive range
  • Applying consistent quantity validation during cart, checkout, and order creation workflows
  • Recalculating prices and totals from trusted product and catalog data on the server
  • Rejecting values that violate product availability, minimum, maximum, or increment rules
  • Avoiding reliance on client-side validation or hidden form fields for security decisions
  • Limiting authenticated account privileges and monitoring unusual cart activity

How teams detect issues like this

Organizations can identify this class of issue through:

  • Static analysis and code review checks for request parameters used directly in pricing logic
  • Tests covering zero, negative, fractional, oversized, missing, and type-confused quantity values
  • Review of all cart and checkout paths for consistent server-side validation
  • Runtime monitoring for anomalous quantities, unusually discounted totals, and repeated cart manipulation
  • API policies requiring schema validation and server-side recalculation of monetary values
  • Automated security testing tools that exercise business-logic and parameter-boundary cases

Sources

SourceLink
github.comgithub.com/isukasanuj/bagisto-cve/blob/main/CVE-2026-79410.md

Frequently asked

questions

Yes, within the application's authenticated attack surface. An attacker generally needs only the ability to submit add-to-cart requests, not access to the server itself.

Yes. The described attack requires an authenticated account that can use the cart functionality.

Validate quantity strictly on the server, enforce product-specific limits, and recalculate cart and order totals from trusted data rather than accepting client-supplied pricing results.

Use centralized input schemas, test boundary and malformed values, apply validation consistently across checkout workflows, and monitor for anomalous quantity and price combinations.

Find out what's already
exploitable in your codebase.