CVE-2025-6342
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-6342 is a critical SQL injection vulnerability in the Online Shoe Store version 1.0, specifically in the /admin/admin_football.php file. The vulnerability occurs because the 'pid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete data remotely without authentication. [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. They can extract sensitive information, modify or delete records, and potentially disrupt or take control of your system. Since exploitation requires no authentication and can be done remotely, it poses a significant threat to data confidentiality, integrity, and availability, potentially affecting 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_football.php endpoint for SQL injection via the 'pid' parameter. Common detection methods include using SQL injection testing tools like sqlmap with payloads such as boolean-based blind injection (using MySQL RLIKE), error-based injection, and time-based blind injection (using MySQL SLEEP function). Additionally, attackers can identify vulnerable targets using Google dorking with the query: inurl:admin/admin_football.php. Example command using sqlmap: sqlmap -u "http://target/admin/admin_football.php?pid=1" --technique=BEUST --dbms=MySQL [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Enforcing strict input validation and filtering on all user-supplied data, especially the 'pid' parameter. 4) Minimizing database user privileges by avoiding use of high-privilege accounts for routine operations. 5) Conducting regular security audits of code and systems to detect and address vulnerabilities promptly. [1, 3, 2]