CVE-2026-15190
Received Received - Intake

SQL Injection in Simple and Nice Shopping Cart Script

Vulnerability report for CVE-2026-15190, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-09

Last updated on: 2026-07-09

Assigner: VulDB

Description

A vulnerability was detected in SourceCodester Simple and Nice Shopping Cart Script 1.0. This affects an unknown part of the file /login.php. Performing a manipulation of the argument Username results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-09
Last Modified
2026-07-09
Generated
2026-07-09
AI Q&A
2026-07-09
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
sourcecodester simple_and_nice_shopping_cart_script 1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Impact Analysis

This vulnerability poses severe risks including unauthorized access to sensitive data, data leakage, data tampering, and potential system compromise.

It can also lead to service disruption and allows attackers to manipulate or extract information from the database without authentication.

Compliance Impact

The SQL injection vulnerability in the Simple and Nice Shopping Cart Script 1.0 allows unauthorized access to sensitive data, data manipulation, and potential system compromise. Such unauthorized access and data leakage can lead to violations of data protection regulations like GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access and breaches.

Failure to protect against this vulnerability could result in non-compliance with these standards, as it undermines data confidentiality, integrity, and availability, which are core requirements of GDPR, HIPAA, and similar regulations.

Executive Summary

The Simple and Nice Shopping Cart Script V1.0 by sourcecodester contains a critical SQL injection vulnerability in the /login.php file. This vulnerability occurs due to improper input validation of the 'username' parameter, which allows attackers to inject malicious SQL queries directly into the database.

Attackers can exploit this flaw remotely without needing login credentials by using techniques such as boolean-based blind or time-based blind SQL injection. This manipulation can alter query logic or introduce delays to extract or manipulate data.

Detection Guidance

This SQL injection vulnerability in /login.php can be detected by testing the 'username' parameter for SQL injection flaws using boolean-based blind or time-based blind SQL injection techniques.

You can use commands or tools that send payloads to the username parameter to observe changes in response or delays, indicating injection points.

  • Example payloads include injecting ' OR 1=1-- or ' OR SLEEP(5)-- to test for boolean or time-based blind SQL injection.
  • Using tools like sqlmap with a command such as: sqlmap -u "http://target/login.php" --data="username=admin&password=pass" --risk=3 --level=5 --batch
Mitigation Strategies

Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection.

Additionally, apply strict input validation and filtering on the 'username' parameter to block malicious input.

Minimize database user permissions to limit the impact of a potential exploit.

Conduct regular security audits to identify and remediate vulnerabilities promptly.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-15190. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart