CVE-2025-11106
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 |
|---|---|---|
| fabian | simple_scheduling_system | 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-11106 is a critical SQL injection vulnerability in the Simple Scheduling System version 1.0, specifically in the file /schedulingsystem/addfaculty.php. It occurs because the 'falname' 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, 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 sensitive data, data leakage, data modification or deletion, and potential full system compromise or service disruption. Since it can be exploited remotely without authentication, attackers can manipulate the database and disrupt business continuity or compromise system security. [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 'falname' parameter in the /schedulingsystem/addfaculty.php endpoint for SQL injection. A proof-of-concept payload uses a time-based blind SQL injection with the MySQL SLEEP() function, for example: falname=123' AND (SELECT 5082 FROM (SELECT(SLEEP(5)))IUCS) AND 'hmGS'='hmGS. Automated tools like sqlmap can be used to confirm the vulnerability by targeting this parameter. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:schedulingsystem/addfaculty.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the 'falname' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, consider replacing the affected software with an alternative product. [1, 2]