CVE-2025-8238
BaseFortify
Publication date: 2025-07-27
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-8238 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 software, specifically in the /admin/update_s2.php file. The vulnerability occurs because the 'credits' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized manipulation of database queries, potentially allowing attackers to access, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting 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. This can disrupt services, compromise data integrity, and severely impact system security and business continuity. The attack can be performed remotely and easily, without requiring any authentication. [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/update_s2.php endpoint for SQL injection via the 'credits' parameter. A proof-of-concept payload uses a time-based blind SQL injection to confirm the flaw, for example: sending a POST request with credits=4' AND (SELECT 2135 FROM (SELECT(SLEEP(5)))YgVY) AND 'MBiI'='MBiI. Additionally, tools like sqlmap can be used to automate detection of this SQL injection vulnerability. Vulnerable targets can also be identified using Google dorking with queries such as "inurl:admin/update_s2.php" to find exposed instances. [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) Applying input validation and filtering to the 'credits' parameter to ensure it conforms to expected formats. 3) Using prepared statements with parameter binding to prevent SQL injection. 4) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. [2, 3]