CVE-2025-8249
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-8249 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 application, specifically in the /admin/update_s3.php file. It occurs because the 'credits' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data leakage, modification, deletion, or full system control. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data tampering, deletion of data, and disruption of services. Attackers can exploit it remotely without any authentication, potentially gaining full control over the affected system. This compromises the confidentiality, integrity, and availability of the system and its data. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the /admin/update_s3.php endpoint for SQL injection on the 'credits' parameter. A proof-of-concept time-based blind SQL injection payload is: credits=4' AND (SELECT 2135 FROM (SELECT(SLEEP(5)))YgVY) AND 'MBiI'='MBiI. You can use tools like sqlmap to automate detection by targeting the vulnerable endpoint with POST data containing the 'credits' parameter. For example, using sqlmap: sqlmap -u "http://target/admin/update_s3.php" --data="credits=4" --technique=T --time-sec=5 [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replace the affected software with an alternative product if possible. 2) Implement prepared statements with parameter binding to prevent SQL injection. 3) Apply strict input validation and filtering on the 'credits' parameter to ensure it conforms to expected formats. 4) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conduct regular security audits of code and systems to identify and fix vulnerabilities promptly. [2, 3]