CVE-2025-11115
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-11115 is a critical SQL injection vulnerability in version 1.0 of the Simple Scheduling System, specifically in the /addtime.php file. The vulnerability occurs because the starttime and endtime parameters are not properly validated or sanitized before being used in SQL queries. This allows remote attackers to inject malicious SQL code without authentication, potentially compromising the database by accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to your database, allowing attackers to leak sensitive information, manipulate or delete data, and potentially disrupt system availability. Since exploitation does not require authentication and can be done remotely, it poses a serious threat to system security and business continuity. [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 /addtime.php endpoint for SQL injection via the starttime and endtime parameters. One method is to use sqlmap to send crafted POST requests targeting these parameters, for example: sqlmap -u "http://target/schedulingsystem/addtime.php" --data="starttime=123&endtime=456" --batch. Additionally, a time-based blind SQL injection payload such as starttime=123' AND (SELECT SLEEP(5)) AND '1'='1 can be used to observe delays indicating vulnerability. Google dorking with queries like inurl:addtime.php can help identify potentially vulnerable targets on the network. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no official patch is available. Additionally, implement prepared statements with parameter binding to prevent SQL injection, enforce strict input validation and filtering on starttime and endtime parameters, and minimize database user privileges by avoiding high-privilege accounts for application access. Conduct regular security audits to detect and address vulnerabilities promptly. [1, 2, 3]