CVE-2025-11107VulnerabilityPublished 28 Sep 2025Updated 29 Sep 2025

CVE-2025-11107: code-projects Simple Scheduling System · SQL Injection

Affects code-projects Simple Scheduling SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% 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:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Simple Scheduling System	Affected =1.0	Fixed in–

AI-suggested

European organizations should immediately audit their use of the Simple Scheduling System version 1.0 and assess exposure to the vulnerable endpoint. 2) Refactor the application code to use parameterized queries or prepared statements to prevent SQL injection. 3) Restrict network access to the scheduling system, limiting it to trusted internal IP ranges or VPN connections. 4) Monitor web server and database logs for suspicious activity related to the addcourse.php endpoint. 5) Employ Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting this parameter. 6) Conduct security awareness training for administrators to recognize signs of exploitation. 7) Plan for an upgrade or replacement of the vulnerable software version once a patch or secure alternative is available. 8) Regularly back up scheduling data and test restoration procedures to minimize impact in case of compromise.

Description

A vulnerability was found in code-projects Simple Scheduling System 1.0. This issue affects some unknown processing of the file /schedulingsystem/addcourse.php. Performing manipulation of the argument corcode results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used.

Impact

For European organizations, this vulnerability could lead to unauthorized access and manipulation of scheduling data, which may include sensitive information about courses, personnel, and resource allocations. Educational institutions, training centers, and businesses relying on the Simple Scheduling System for operational planning are at risk of data breaches, service disruption, and reputational damage. The compromise of scheduling data could also facilitate further attacks, such as social engineering or insider threat exploitation. Given the remote and unauthenticated nature of the exploit, attackers could leverage this vulnerability to gain a foothold within the network or exfiltrate confidential information. The medium severity rating suggests moderate impact, but the availability of a public exploit increases the urgency for mitigation. Additionally, disruption to scheduling systems can affect operational continuity, especially in sectors where precise timing and resource management are critical. European data protection regulations, such as GDPR, impose strict requirements on data security, and exploitation of this vulnerability could lead to regulatory penalties and legal consequences if personal data is exposed.

Summary

CVE-2025-11107 identifies a SQL injection vulnerability in the Simple Scheduling System version 1.0 developed by code-projects. The vulnerability resides in the /schedulingsystem/addcourse.php script, where the corcode parameter is improperly sanitized, allowing an attacker to inject malicious SQL commands. This flaw can be exploited remotely without authentication or user interaction, making it accessible to any attacker with network access to the affected system. Exploitation could allow attackers to read, modify, or delete sensitive scheduling data stored in the backend database, potentially compromising the confidentiality and integrity of organizational data. The vulnerability does not require privileges or user interaction, increasing its risk profile. Although no active exploits have been observed in the wild, a public exploit is available, which could facilitate automated attacks or targeted exploitation. The CVSS 4.0 base score of 6.9 reflects a medium severity, considering the network attack vector, low complexity, and lack of required privileges. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet, indicating that organizations must implement interim mitigations. The lack of scope change means the impact is confined to the affected component, but the potential for data compromise remains significant. This vulnerability highlights the importance of secure coding practices such as input validation and parameterized queries in web applications handling critical scheduling data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Oct 2025, 00:37 UTC

Technical details

References

Community reviews

Related threats