CVE-2025-11108: code-projects Simple Scheduling System · SQL Injection
Affects code-projects Simple Scheduling SystemSource CVE Database V5
Public exploit available · CVSS 6.9 Medium.
Data as of 9 Nov 2026, 23:23 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| code-projects Simple Scheduling System | Affected
| Fixed in– |
AI-suggested
- Immediately implement input validation and sanitization for the 'room' parameter in /schedulingsystem/addroom.php to reject or properly escape malicious SQL syntax.
- Refactor the code to use parameterized queries or prepared statements to eliminate direct concatenation of user input into SQL commands.
- Restrict network exposure of the scheduling system by placing it behind firewalls and limiting access to trusted internal networks or VPNs.
- Monitor logs for unusual SQL errors or suspicious activity indicative of injection attempts.
- Conduct a thorough code review of the entire application to identify and remediate similar injection flaws.
- Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.
- Educate developers on secure coding practices to prevent future injection vulnerabilities.
- Consider deploying Web Application Firewalls (WAFs) with SQL injection detection rules as an interim protective measure.
- Regularly back up scheduling data and test restoration procedures to mitigate potential data loss from exploitation.
Description
A vulnerability was determined in code-projects Simple Scheduling System 1.0. Impacted is an unknown function of the file /schedulingsystem/addroom.php. Executing manipulation of the argument room can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.