CVE-2025-11107
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?
This vulnerability is a critical SQL injection flaw in the Simple Scheduling System version 1.0, specifically in the file /schedulingsystem/addcourse.php. It occurs because the 'corcode' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating the database in unauthorized ways. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, deletion, and exposure of sensitive information. Attackers may gain full system control and cause service disruption. Since no authentication is required, the risk is high, potentially threatening 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 SQL injection vulnerability can be detected by testing the vulnerable parameter 'corcode' in the /schedulingsystem/addcourse.php file for injection flaws. A proof-of-concept payload uses a time-based blind SQL injection to cause a delay in the database response, for example: corcode=123' AND (SELECT 6155 FROM (SELECT(SLEEP(5)))FDwS) AND 'pCJb'='pCJb. You can use tools like sqlmap to automate detection by targeting the URL with the vulnerable parameter. Additionally, Google dorking with the query 'inurl:schedulingsystem/addcourse.php' can help identify vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'corcode' 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 component with an alternative product. [1, 2, 3]