CVE-2025-6307
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-6307 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /function/edit_customer.php file. It occurs because the application does not properly validate or sanitize the 'firstname' parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, modification, or deletion of sensitive information, and potentially full system compromise or service disruption. It impacts the confidentiality, integrity, and availability of the affected system, posing severe 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 checking for the presence of the vulnerable endpoint '/function/edit_customer.php' and testing the 'firstname' parameter for SQL injection. One method is to use Google dorking with the query 'inurl:function/edit_customer.php' to identify potentially vulnerable targets. For active testing, you can use tools like sqlmap or manual curl commands to inject SQL payloads into the 'firstname' parameter and observe the response for SQL errors or unexpected behavior. Example curl command: curl -G 'http://target.com/function/edit_customer.php' --data-urlencode "firstname=' OR '1'='1". Additionally, monitoring logs for unusual SQL errors or suspicious input patterns targeting 'firstname' can help detect exploitation attempts. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements (parameterized queries) to ensure user inputs like 'firstname' are treated as data, not executable SQL code. 2) Apply strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimize database user privileges by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace or update the affected software to a version without this vulnerability or use an alternative product. [2]