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

CVE-2025-11105: 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 25 Oct 2026, 19:02 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-25.

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

1. Immediate code review and remediation: Implement parameterized queries or prepared statements in the /schedulingsystem/addsubject.php file to prevent SQL injection. 2. Input validation: Enforce strict validation and sanitization of all user-supplied inputs, especially the 'subcode' parameter, to reject malicious payloads. 3. Network segmentation and access controls: Restrict access to the scheduling system to trusted internal networks or VPNs to reduce exposure. 4. Web application firewall (WAF): Deploy or update WAF rules to detect and block SQL injection attempts targeting this endpoint. 5. Monitoring and logging: Enable detailed logging of database queries and web requests to detect anomalous activity indicative of exploitation attempts. 6. Patch management: Monitor vendor announcements for official patches or updates and apply them promptly once available. 7. Incident response readiness: Prepare to respond to potential breaches by having data backups, forensic capabilities, and communication plans in place. 8. User awareness: Inform relevant IT and security teams about the vulnerability and ensure they understand the risk and mitigation steps.

Description

A flaw has been found in code-projects Simple Scheduling System 1.0. This affects an unknown part of the file /schedulingsystem/addsubject.php. This manipulation of the argument subcode causes sql injection. Remote exploitation of the attack is possible. The exploit has been published and may be used.

Impact

For European organizations, exploitation of this SQL injection vulnerability could lead to unauthorized access to sensitive scheduling data, including potentially personal or operational information. This could result in data breaches violating GDPR and other privacy regulations, leading to legal and financial repercussions. Integrity of scheduling data could be compromised, causing operational disruptions, mismanagement of resources, or denial of service if critical scheduling functions are affected. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, especially in sectors relying heavily on scheduling systems such as education, healthcare, and public administration. The medium severity suggests moderate but tangible risk, particularly for organizations that have not implemented compensating controls or are slow to patch. The absence of known active exploits currently provides a window for proactive defense, but the published exploit code means attackers could rapidly weaponize this vulnerability.

Summary

CVE-2025-11105 identifies a SQL injection vulnerability in the Simple Scheduling System version 1.0 developed by code-projects. The flaw exists in the /schedulingsystem/addsubject.php script, where the 'subcode' parameter is improperly sanitized, allowing attackers to inject arbitrary SQL queries. This vulnerability can be exploited remotely without requiring authentication or user interaction, making it accessible to a wide range of attackers. The injection can lead to unauthorized reading, modification, or deletion of database records, potentially compromising sensitive scheduling data. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no active exploits have been observed in the wild, the public availability of exploit code increases the likelihood of exploitation attempts. The vulnerability affects only version 1.0 of the product, and no official patches have been linked yet. The lack of secure coding practices, such as parameterized queries or input validation, is the root cause. Organizations relying on this scheduling system should assess their exposure and implement mitigations promptly.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats