CVE-2025-11114
BaseFortify
Publication date: 2025-09-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 |
|---|---|---|
| codeastro | online_leave_application | 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-11114 is a critical SQL injection vulnerability in CodeAstro Online Leave Application 1.0, specifically in the file /leaveAplicationForm.php. It occurs because the application improperly handles the 'absence[]' parameter, allowing attackers to inject malicious SQL code. This can be exploited remotely without authentication. The flaw enables attackers to execute unauthorized SQL commands, potentially leading to unauthorized database access, data leakage, modification, deletion, or full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, modification or deletion of data, and potential full system compromise. It can also disrupt services by exploiting the SQL injection flaw. Attackers can remotely exploit this vulnerability without needing authentication, increasing the risk to affected systems. [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 /leaveAplicationForm.php endpoint for SQL injection via the absence[] parameter. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/leaveAplicationForm.php" --data="absence[]=Sick" --batch --level=5 --risk=3. Additionally, manual testing can be done by injecting payloads such as error-based or time-based SQL injection strings into the absence[] parameter and observing the response or delay. For example, injecting a payload that triggers a delay (e.g., using SLEEP(5)) can confirm the vulnerability if the response is delayed. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, applying strict input validation and filtering on the absence[] parameter, and minimizing database user permissions by avoiding high-privilege accounts for the application database connection. Conducting regular security audits to detect and fix vulnerabilities promptly is also recommended. If possible, consider replacing the affected component with a secure alternative. [1, 2, 3]