CVE-2025-6343
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-6343 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /admin/admin_product.php file. It occurs because the 'pid' 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 leading to unauthorized database access, data leakage, modification, deletion, or full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data modification or deletion, exposure of confidential information, disruption of service, and potentially full system compromise. Since it can be exploited remotely without authentication and has publicly available proof-of-concept exploits, attackers can easily target vulnerable systems, leading to significant security breaches and loss of data integrity and availability. [1, 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 'pid' parameter in the /admin/admin_product.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection. Example sqlmap command: sqlmap -u "http://target/admin/admin_product.php?pid=1" --batch --dbs. Additionally, manual testing can be done using payloads such as: - pid=28' RLIKE (SELECT (CASE WHEN (1636=1636) THEN 28 ELSE 0x28 END))-- - pid=28' AND (SELECT 9403 FROM(SELECT COUNT(*),CONCAT(0x71786b7871,(SELECT (ELT(9403=9403,1))),0x7171626b71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- - pid=28' AND (SELECT 9537 FROM (SELECT(SLEEP(5)))DNeL)-- These payloads test for boolean-based blind, error-based, and time-based SQL injection respectively. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Apply strict input validation and filtering to ensure the 'pid' parameter only accepts expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts (such as root or admin) for routine database operations. - Conduct regular security audits to detect and address vulnerabilities promptly. - If possible, replace the affected product with an alternative solution as no known countermeasures currently exist. These actions help prevent SQL injection attacks, protect data integrity, and maintain system security. [3, 2]