CVE-2025-6354
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
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Attackers can modify, delete, or expose sensitive data. Since the attack requires no authentication and can be launched remotely, it poses a significant risk to system confidentiality, integrity, and availability. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-6354 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /function/customer_signup.php file. The vulnerability occurs because the 'email' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables attackers to manipulate SQL queries, potentially gaining unauthorized access to the database, modifying or deleting data, and exposing sensitive information. The attack can be performed remotely without authentication. [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 'email' parameter in the /function/customer_signup.php endpoint for SQL injection. You can use tools like sqlmap to automate detection. Example command: sqlmap -u "http://targetsite/function/customer_signup.php" --data="[email protected]" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads such as 'email=codeprojects@qqq' AND 3434=3434 AND 'UkVq'='UkVq' to check for boolean-based blind SQL injection, or time-based payloads using SLEEP() to infer injection points. [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. 2) Apply strict input validation and filtering on the 'email' 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 identify and fix vulnerabilities promptly. If possible, replace the affected software with an alternative product as no known countermeasures are documented. [1, 3, 2]