CVE-2025-8253
BaseFortify
Publication date: 2025-07-28
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 | exam_form_submission | 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-8253 is a critical SQL injection vulnerability in the code-projects Exam Form Submission version 1.0, specifically in the /admin/delete_s6.php file. It occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL commands. This flaw enables remote attackers to manipulate the database by executing unauthorized SQL queries without any authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, allowing attackers to extract sensitive data, modify or delete records, and potentially gain full control over the affected system. It can also cause service disruptions, threatening 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 testing the 'id' parameter in the /admin/delete_s6.php URL for SQL injection. A common method is to use tools like sqlmap to automate detection. For example, you can run a command such as: sqlmap -u "http://targetsite/admin/delete_s6.php?id=1" --risk=3 --level=5 --batch to test for SQL injection. Additionally, a proof-of-concept payload for time-based blind SQL injection is: id=10'+(SELECT 0x4f495378 WHERE 3243=3243 AND (SELECT 1096 FROM (SELECT(SLEEP(5)))hGgM))+' which can be used to manually test if the system delays response, indicating vulnerability. Searching for the vulnerable endpoint using Google dorking with inurl:admin/delete_s6.php can help identify affected systems. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with a secure alternative if possible. If replacement is not feasible, implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. Enforce strict input validation and filtering on the 'id' parameter to ensure only expected input is accepted. Minimize database user privileges by avoiding use of high-privilege accounts for routine database operations. Conduct regular security audits to detect and address vulnerabilities promptly. Since no known countermeasures are officially identified, these best practices are critical to reduce risk. [1, 2, 3]