CVE-2025-10833
BaseFortify
Publication date: 2025-09-23
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 1000projects | bookstore_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10833 is a critical SQL injection vulnerability in version 1.0 of the 1000projects Bookstore Management System, specifically in the /login.php file. The vulnerability occurs because the 'unm' (username) parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database by retrieving, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve sensitive information, modify or delete data, and potentially cause full system compromise or service disruption. Since it requires no authentication and can be exploited remotely, it poses a significant risk to data confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'unm' parameter in the /login.php file for SQL injection. Commands using sqlmap or manual injection payloads can be used. For example, using sqlmap: sqlmap -u "http://target/login.php?unm=1" --batch --dbs. Manual payloads include Boolean-based blind SQL injection like: unm=-2611' OR 8649=8649# or time-based blind SQL injection like: unm=1' AND (SELECT SLEEP(5))--. Additionally, Google Dorking with queries such as "inurl:login.php" can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include using prepared statements with parameter binding to prevent SQL injection, implementing strict input validation and filtering on the 'unm' parameter, minimizing database user permissions by avoiding high-privilege accounts for routine operations, and conducting regular security audits. If possible, replacing the affected software with an alternative product is also recommended. [2, 3]