CVE-2026-71248
Received Received - Intake

SQL Injection and Unauthenticated Deletion in Inventory Management System PHP

Publication date: 2026-08-05

Last updated on: 2026-08-05

Assigner: 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c

Description
Inventory-Management-System-PHP's login.php constructs its authentication query via direct string concatenation of raw POST parameters: $sql = "select * from user where email = '$email' and password = '$password'", with no escaping or parameterization, allowing authentication bypass via a payload such as email=' OR 1=1 LIMIT 1-- -. Separately, delete.php executes mysqli_query($db, "DELETE FROM product WHERE product_id=" . $_GET['id']) with no authentication check and no validation of the id parameter, allowing an unauthenticated attacker to delete arbitrary product rows or perform blind SQL injection via payloads such as id=0 OR SLEEP(5).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-05
Last Modified
2026-08-05
Generated
2026-08-05
AI Q&A
2026-08-05
EPSS Evaluated
N/A
NVD
CVE-2026-71248
EUVD
EUVD-2026-53321

Affected Vendors & Products

Currently, no data is known.

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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves two SQL injection flaws in an inventory management system. In login.php, user input for email and password is directly concatenated into an SQL query without sanitization, allowing attackers to bypass authentication by injecting malicious SQL payloads like ' OR 1=1 LIMIT 1-- -. In delete.php, the product ID parameter is directly inserted into a DELETE query without validation, enabling unauthenticated attackers to delete arbitrary database rows or perform blind SQL injection.

Detection Guidance

Check login.php and delete.php for direct SQL query construction using string concatenation of user inputs. Test with payloads like email=' OR 1=1 LIMIT 1-- - in login forms or id=0 OR SLEEP(5) in delete requests. Monitor for unexpected database queries or errors.

Impact Analysis

An attacker could gain unauthorized access to the system by bypassing login, delete or modify product data, or extract sensitive information from the database. This could lead to data loss, corruption, or unauthorized changes to inventory records, disrupting business operations.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and security. GDPR mandates protection of personal data, and HIPAA requires safeguards for protected health information. The lack of authentication and SQL injection risks could lead to unauthorized data access or breaches, resulting in legal penalties and reputational damage.

Mitigation Strategies

Replace direct SQL query construction with parameterized prepared statements in login.php and delete.php. Ensure delete.php validates and casts the id parameter to an integer. Implement authentication checks for all state-changing endpoints.

Chat Assistant

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

EPSS Chart