CVE-2025-14668
BaseFortify
Publication date: 2025-12-14
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 |
|---|---|---|
| campcodes | advanced_online_examination_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-14668 is a critical SQL injection vulnerability in the Advanced Online Examination System version 1.0, specifically in the file /query/loginExe.php. The vulnerability occurs because the 'username' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data tampering, and full system control. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of data, disruption of service, and potentially full control over the affected system. Since the attack can be performed remotely without authentication, it poses a high risk of exploitation leading to confidentiality, integrity, and availability breaches. [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 loginExe.php endpoint for SQL injection using crafted payloads targeting the 'username' parameter. For example, a time-based blind SQL injection payload such as: username=admin@password' AND (SELECT 4225 FROM (SELECT(SLEEP(5)))ZXtc) AND 'AtoL'='AtoL&pass=111 can be used to observe delayed responses indicating injection. Tools like sqlmap can automate detection by targeting the URL with POST data. Example sqlmap command: sqlmap -u "http://<target>/Online%20Examination%20System/query/loginExe.php" --data="username=admin%40password&pass=111" --time-sec=5 --technique=T [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'username' parameter to ensure only expected formats are accepted. 3) Minimize database user privileges by avoiding use of high-privilege accounts for routine database operations. 4) Conduct regular security audits and code reviews to identify and fix vulnerabilities promptly. If possible, replace the affected software with a secure alternative. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, data leakage, and data tampering through SQL injection, which compromises the confidentiality, integrity, and availability of sensitive data. Such security breaches can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive information. Therefore, this vulnerability negatively impacts compliance by exposing sensitive data to unauthorized parties and risking data integrity. [1, 2, 3]