CVE Alert: CVE-2025-11654 – yousaf530 – Inferno Online Clothing Store

CVE-2025-11654

HIGHNo exploitation known

A vulnerability was identified in yousaf530 Inferno Online Clothing Store up to 827dd42bfbe380e8de76fdc67958c24cf1246208. The affected element is an unknown function of the file /log.php. Such manipulation of the argument cemail/password leads to sql injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3.1 (7.3)
Vendor
yousaf530
Product
Inferno Online Clothing Store
Versions
827dd42bfbe380e8de76fdc67958c24cf1246208
CWE
CWE-89, SQL Injection
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Published
2025-10-13T01:02:06.914Z
Updated
2025-10-13T01:02:06.914Z

AI Summary Analysis

Risk verdict

Publicly released PoC enables remote SQL injection against the log.php endpoint with no authentication, creating immediate risk to data integrity and availability.

Why this matters

For an online clothing store, SQL injection can exfiltrate customer data, alter orders, or deface listings, with potential financial loss and reputational damage. The advisory notes a public exploit and medium–high CVSS impact, indicating realistic attacker interest and rapid weaponisation potential.

Most likely attack path

No user interaction is required; an attacker can send crafted input to the cemail/password parameter over the network. With AV:N/AC:L/PR:N/UI:N and full CIA impact, the vulnerability enables direct access to the backend DB from the public web tier, risking lateral movement within the application if other insecure endpoints exist.

Who is most exposed

Public-facing e-commerce sites using PHP-based storefronts, especially on shared or cloud VMs with rolling-release deployments, are at highest risk.

Detection ideas

  • Web server logs show SQL error signatures from log.php requests.
  • POSTs to log.php contain anomalous or SQL-like payloads in cemail/password.
  • Spikes or anomalies in database error rates and query latency.
  • WAF/IDS alerts targeting SQL injection patterns on login-related endpoints.
  • Repeated failed login or unusual user enumeration attempts from diverse IPs.

Mitigation and prioritisation

  • Apply vendor patch or upgrade to fixed release; test before production.
  • If patching isn’t feasible, implement parameterised queries and strict input validation; disable verbose DB errors.
  • Enforce least-privilege DB credentials and separate web/app DB accounts.
  • Enable WAF/RAAS rules and monitor for SQLi indicators; implement network allowlisting where practical.
  • Change-management: test in staging, document rollback, and schedule deployment with monitoring.
  • If KEV true or EPSS ≥ 0.5, treat as priority 1.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.