CVE-2025-11108
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-11108 is a critical SQL injection vulnerability in version 1.0 of the Simple Scheduling System, specifically in the file /schedulingsystem/addroom.php. It occurs because the 'room' parameter is improperly handled and directly used in SQL queries without proper sanitization or validation. This allows an attacker to remotely inject malicious SQL commands, potentially manipulating the database. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, extraction of sensitive information, modification or deletion of data, full system control by attackers, and disruption of service availability. Since no authentication is required to exploit it, attackers can remotely perform these actions, threatening confidentiality, integrity, and availability of the system. [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 /schedulingsystem/addroom.php endpoint for SQL injection via the 'room' parameter. A proof-of-concept payload uses a time-based blind SQL injection with a delay, such as: room=123' AND (SELECT 1619 FROM (SELECT(SLEEP(5)))sHgr) AND 'XIGv'='XIGv. Tools like sqlmap can be used to automate detection by sending crafted POST requests to this endpoint with malicious 'room' parameters. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:schedulingsystem/addroom.php. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'room' parameter, minimizing database user permissions by avoiding high-privilege accounts for routine operations, and conducting regular security audits of the code and system. Since no known countermeasures currently exist for this specific vulnerability, replacing the affected component with an alternative product is also suggested. [1, 2, 3]