External risk intelligence

ReadyEcommerce Unauthenticated SQL Injection Affecting Product Listing API.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-63106

The vulnerability exists in a product listing API endpoint within an e-commerce application. By design, e-commerce product catalogs and their associated APIs are intended to be public-facing to enable customer browsing and interaction, making this surface reachable from the internet in normal, default deployments.

SQL Injection

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in ReadyEcommerce software that could allow attackers to access sensitive database information, including user credentials and administrator passwords, potentially leading to unauthorized system access and further compromise.

  • Unauthenticated SQL injection in product API.
  • Impacts sensitive data, including credentials.
  • Confirm relevance and understand potential exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could exploit this vulnerability by sending a specially crafted request to the product listing API. This request would target the `rating` parameter within the `products` endpoint, which is improperly handled by the `ProductController.php` file. By manipulating this parameter, an attacker can inject malicious SQL code into the database query, potentially leading to the disclosure of sensitive information, including user credentials and administrator password hashes, and possibly gaining further access to the system.

  • No authentication or privileges are required.
  • A request to the product listing API triggers the vulnerability.
  • Risk includes data theft and potential system compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to extract sensitive database contents, potentially including user credentials and administrator password hashes. When supported by the advisory, this could also lead to additional file system access if the database connection is running as root.

  • Database contents and user credentials at risk.
  • Injection via unsanitized product listing API parameter.
  • Full database extraction and potential file access.

Operational Fix

Recommended remediation, mitigation, and detection steps

The application owner is responsible for this vulnerability. The first step is to identify all instances of the affected e-commerce application, confirm its reachability, and determine business criticality to prioritize remediation.

  • Application owner must remediate.
  • Verify external exposure and business criticality.
  • Plan and execute remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is ReadyEcommerce?

ReadyEcommerce is a multi-vendor e-commerce platform designed for building online storefronts, mobile apps, and management systems. It provides the core functionality needed to list products and manage transactions, relying on backend APIs to serve catalog data to customers.

How does CVE-2026-63106 work?

This vulnerability is an SQL injection, which falls under the CWE-89 weakness class. It occurs because the software fails to sanitize input in the product API's rating parameter before using it in a database query. This allows an attacker to manipulate the query to access unauthorized data.

What triggers this SQL injection flaw?

The bug is triggered by sending a specially crafted request to the product listing API endpoint. It does not require any user account or special privileges to execute. Requests that do not interact with the specific rating parameter in the products endpoint do not trigger this vulnerability.

Why is this CVE relevant to my network?

According to Halo Surface Signal, this vulnerability is very likely relevant because e-commerce product APIs are designed to be public-facing. This means the affected component is typically reachable from the internet by default, making it accessible to potential external attackers.

How should I respond to this threat?

First, locate all running instances of the ReadyEcommerce application within your environment. Verify whether these instances are exposed to the internet and assess their business importance to prioritize your response actions.

References