CVE-2025-11105
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-11105 is a critical SQL injection vulnerability in version 1.0 of the Simple Scheduling System, specifically in the file /schedulingsystem/addsubject.php. The vulnerability occurs because the 'subcode' parameter is improperly handled and used directly in SQL queries without proper sanitization or validation. This allows remote attackers to inject malicious SQL commands, potentially manipulating the database without any authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, extraction of sensitive data, modification or deletion of records, and disruption of service availability. Attackers can gain full control over the system's database remotely without authentication, threatening confidentiality, integrity, and availability of the system and its data. [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/addsubject.php endpoint for SQL injection via the 'subcode' parameter. One method is to use sqlmap with a POST request targeting this endpoint. For example, a command like: sqlmap -u "http://target/schedulingsystem/addsubject.php" --data="subcode=123" --risk=3 --level=5 can be used to detect SQL injection. Additionally, a time-based blind SQL injection payload such as 'subcode=123' AND (SELECT 4070 FROM (SELECT(SLEEP(5)))ZVti) AND 'RHvE'='RHvE' can be sent via curl or other HTTP tools to observe response delays indicating vulnerability. Also, Google dorking with queries like inurl:schedulingsystem/addsubject.php can help identify vulnerable targets. [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 'subcode' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Additionally, replacing the affected software with an alternative product is suggested since no known mitigations are documented. Conducting regular security audits to detect and address vulnerabilities promptly is also recommended. [1, 2, 3]