CVE-2025-15243
SQL Injection in Simple Stock System 1.0 /market/login.php
Publication date: 2025-12-30
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 |
|---|---|---|
| code-projects | simple_stock_system | 1.0 |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15243 is a SQL injection vulnerability in the Simple Stock System version 1.0, specifically in the /market/login.php file. The vulnerability occurs because the 'username' parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries, potentially leading to unauthorized database access and other malicious actions. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, sensitive data leakage, data tampering, full system control, and potential service disruption. Attackers can exploit it remotely without any authentication, making it easy to perform attacks that compromise confidentiality, integrity, and availability of the system. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the login.php endpoint, specifically the 'username' parameter, for SQL injection flaws. One common approach is to use automated tools like sqlmap to test for injection by sending crafted POST requests to /market/login.php with manipulated 'username' inputs. For example, a command using sqlmap could be: sqlmap -u "http://target/market/login.php" --data="username=admin'--&password=anything" --risk=3 --level=5. Additionally, attackers may be identified by monitoring for unusual or suspicious POST requests targeting /market/login.php with SQL injection payloads. Google dorking such as searching for inurl:market/login.php can help identify vulnerable targets externally. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding in the login.php code to separate SQL commands from user inputs, preventing injection. 2) Apply strict input validation and filtering on the 'username' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) If possible, replace the affected Simple Stock System 1.0 with an alternative solution that is not vulnerable. These corrective actions are critical to protect system security and maintain data integrity. [2, 3, 1]