CVE-2025-6316
BaseFortify
Publication date: 2025-06-20
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 | online_shoe_store | 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-6316 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /admin/admin_running.php file. It occurs because the 'qty' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers 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? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. Attackers can exploit it remotely without authentication to execute arbitrary SQL commands, which threatens the confidentiality, integrity, and availability of the system and its data, posing significant risks to system security and business continuity. [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 /admin/admin_running.php endpoint for SQL injection via the 'qty' parameter in multipart/form-data POST requests. Tools like sqlmap can be used to automate detection by targeting this parameter. Additionally, time-based blind SQL injection can be tested using payloads that invoke database functions such as MySQL's SLEEP(). Attackers may also be identified by monitoring for unusual POST requests to /admin/admin_running.php containing suspicious 'qty' values. Google dorking with queries like 'inurl:admin/admin_running.php' can help identify exposed instances. Example command using sqlmap: sqlmap -u "http://target/admin/admin_running.php" --data="qty=1" --method=POST --technique=T --batch [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'qty' parameter to ensure it conforms to expected formats. 3) Minimize database user privileges by avoiding use of high-privilege accounts for routine database operations. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. If possible, replace or update the affected component to a secure version. Monitoring and restricting access to /admin/admin_running.php can also reduce exposure. [2]