CVE-2025-8251
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-8251 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 application, specifically in the /admin/delete_s4.php file. The vulnerability occurs because the 'ID' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL commands. This can be exploited remotely without authentication, enabling attackers to manipulate database queries and potentially compromise the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to gain unauthorized access to your database, extract sensitive information, modify or delete data, and potentially take control of the affected system. It can also lead to 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 /admin/delete_s4.php endpoint for SQL injection via the 'id' parameter. A proof-of-concept payload for a time-based blind SQL injection is: id=10'+(SELECT 0x4f495378 WHERE 3243=3243 AND (SELECT 1096 FROM (SELECT(SLEEP(5)))hGgM))+' . You can use tools like sqlmap to automate detection by targeting the URL with the vulnerable parameter. Additionally, Google dorking with the query inurl:admin/delete_s4.php can help identify vulnerable targets on your network or externally. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing or patching the affected component, as no known countermeasures are documented; 2) Using prepared statements with parameter binding to prevent SQL injection; 3) Implementing strict input validation and filtering on the 'id' parameter; 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations; and 5) Conducting regular security audits to detect and fix vulnerabilities promptly. [1, 2, 3]