CVE-2025-10833

7.3

1000projects · Bookstore Management System

1000projects Bookstore Management System 1.0 contains a SQL injection vulnerability in the login.php file, allowing remote attackers to manipulate the unm argument.

Executive summary

The 1000projects Bookstore Management System 1.0 is affected by a critical SQL injection vulnerability that allows remote, unauthenticated attackers to compromise the application database.

Vulnerability

This vulnerability is a SQL injection flaw (CWE-89) located in the login.php file, which fails to properly sanitize the unm argument. The attack vector is network-based and requires no authentication to execute, allowing an attacker to inject malicious SQL commands directly into the backend database.

Business impact

Successful exploitation of this vulnerability could lead to unauthorized access to sensitive bookstore data, potential modification of records, or the loss of data integrity. With a CVSS score of 7.3, this high-severity flaw poses a significant risk to the confidentiality and availability of the management system, potentially enabling attackers to bypass authentication mechanisms entirely.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict access to the login.php endpoint using network-level controls or block the application until a security update is released by the vendor.

Proactive Monitoring: Review application logs for anomalous SQL syntax or unexpected query patterns originating from the login interface.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection patterns specifically targeting the unm parameter in login requests.

Exploitation status

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the referenced GitHub issue.

Analyst recommendation

Given the availability of a public proof-of-concept and the unauthenticated nature of the attack, this vulnerability represents a significant risk. Administrators must prioritize isolating the affected system from public network access until the vendor provides a formal security update to remediate the underlying code vulnerability.

Sources

Originally found and disclosed by xingrenlvke (VulDB User), per the CVE Program record.