CVE-2025-6304
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-6304 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /cart.php file. It occurs because the application improperly handles the 'qty[]' parameter, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access, data leakage, modification, or deletion. The vulnerability can be exploited remotely without authentication, making it highly accessible and dangerous. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to gain unauthorized access to your database, potentially exposing sensitive information, modifying or deleting data, and disrupting services. It can lead to full system compromise and business continuity issues. Since exploitation requires no authentication and is easy to perform, it poses a significant security risk. [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 /cart.php endpoint for SQL injection via the qty[] parameter. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://targetsite/cart.php" --data="pid[]=961461&qty[]=1" --batch --level=5 --risk=3. Additionally, manual testing can be done using proof-of-concept payloads such as: pid[]=961461&qty[]=1' RLIKE (SELECT (CASE WHEN (6527=6527) THEN 1 ELSE 0x28 END)) OR 'WntB'='wzJK and pid[]=961461&qty[]=1' AND (SELECT 7339 FROM (SELECT(SLEEP(5)))CRAa) OR 'cSqZ'='JaCR to observe boolean-based and time-based blind SQL injection behavior. [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 qty[] parameter to ensure only expected numeric values are accepted. 3) Minimize database user permissions by avoiding use of high-privilege accounts for the application database connection. 4) Conduct regular security audits to identify and fix vulnerabilities promptly. If possible, replace the affected product with a secure alternative as no known effective countermeasures currently exist. [2, 3]