CVE-2025-8252
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-8252 is a critical SQL injection vulnerability in the code-projects Exam Form Submission version 1.0, specifically in the /admin/delete_s5.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of the database, such as retrieving, modifying, or deleting data without permission. The attack can be launched remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, allowing attackers to extract sensitive information, modify or delete records, and potentially gain full control over the affected system. It can disrupt services and compromise data integrity, confidentiality, and availability, posing significant 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 testing the /admin/delete_s5.php endpoint for SQL injection via the 'id' parameter. A practical method is to use sqlmap with a command like: sqlmap -u "http://<target>/admin/delete_s5.php" --data="id=10" --batch --dbs --level 5. Additionally, a time-based blind SQL injection payload can be used to confirm the vulnerability, such as: id=10'+(SELECT 0x4f495378 WHERE 3243=3243 AND (SELECT 1096 FROM (SELECT(SLEEP(5)))hGgM))+' . Attackers can also identify vulnerable targets using Google dorking with the query: inurl:admin/delete_s5.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected component with an alternative product if possible. If not, implement prepared statements with parameter binding to prevent SQL injection, enforce strict input validation and filtering on the 'id' parameter, and limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. Conduct regular security audits to detect and address vulnerabilities promptly. [2, 3, 1]