CVE-2025-8240
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-8240 is a critical SQL injection vulnerability in the code-projects Exam Form Submission version 1.0, specifically in the /user/dashboard.php file. It occurs due to improper handling and inadequate validation of the 'phone' parameter, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, letting attackers retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, and potential full system control. Attackers can manipulate SQL queries to retrieve sensitive information, modify or delete data, and disrupt services. Since the attack can be launched remotely without authentication, it poses a significant risk to data integrity, confidentiality, and availability. [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 /user/dashboard.php endpoint for SQL injection via the 'phone' parameter. A proof-of-concept uses a time-based blind SQL injection payload with a SLEEP(5) command sent through the MULTIPART phone POST parameter. Tools like sqlmap can be used to automate detection by targeting this parameter. Additionally, attackers may be identified by monitoring for unusual requests containing SQL injection patterns or by using Google dorking with the query "inurl:user/dashboard.php" to find vulnerable instances. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'phone' parameter to ensure it conforms to expected formats, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Regular security audits should also be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected software with an alternative product is suggested as no known mitigations are documented. [2, 3, 1]