CVE-2025-8326
BaseFortify
Publication date: 2025-07-30
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-8326 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 application, specifically in the /admin/delete_s7.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 accessing, modifying, or deleting data. The vulnerability can be exploited remotely without authentication, and public exploits are available. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, deletion of data, and potentially full system control. Attackers can disrupt services, compromise data integrity and confidentiality, and cause significant damage to the affected system. Since no authentication is required, the risk of exploitation is high and immediate remediation is necessary. [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 vulnerable parameter 'id' in the /admin/delete_s7.php file for SQL injection. One method is to use time-based blind SQL injection payloads, such as injecting a payload that causes a delay (e.g., using the MySQL SLEEP function) to confirm the injection. An example payload is: id=10'+(SELECT 0x4f495378 WHERE 3243=3243 AND (SELECT 1096 FROM (SELECT(SLEEP(5)))hGgM))+' . Additionally, automated tools like sqlmap can be used to test and enumerate databases via the vulnerable parameter. Network detection can also include monitoring for unusual or suspicious HTTP requests targeting /admin/delete_s7.php with SQL injection patterns. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering to ensure inputs conform to expected formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replacing the affected component with an alternative product is recommended since no known countermeasures exist. These steps help protect system security and maintain data integrity. [2, 3]