CVE-2025-8269
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-8269 is a critical SQL injection vulnerability in the Exam Form Submission 1.0 application, specifically in the /admin/delete_s1.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 access to the database, allowing attackers to 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 modify or delete data, disrupt services, and compromise the confidentiality, integrity, and availability of the affected system. The attack can be performed remotely without any authentication, making it highly accessible and dangerous. [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 'id' parameter in the /admin/delete_s1.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection, for example: sqlmap -u "http://target/admin/delete_s1.php?id=1" --batch --dbs. Additionally, time-based blind SQL injection techniques can be used by injecting payloads such as 'id=1 AND SLEEP(5)' to observe response delays indicating vulnerability. Google dorking with queries like inurl:admin/delete_s1.php can help identify potentially vulnerable targets on your network. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying strict input validation and filtering on the 'id' parameter to ensure it conforms to expected formats. 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and fix vulnerabilities promptly. [2, 3, 1]