Skip to main content
CVE-2025-11115VulnerabilityPublished

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

Affects code-projects Simple Scheduling SystemSource CVE Database V5

0

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 40% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
code-projects Simple Scheduling SystemAffected
  • =1.0
Fixed in–

AI-suggested

Since no official patches are currently available, European organizations should immediately implement input validation and sanitization on the starttime and endtime parameters within /addtime.php or at the web application firewall (WAF) level. Employ parameterized queries or prepared statements to prevent SQL injection. Conduct a thorough code review of the scheduling system to identify and remediate other potential injection points. Deploy network-level protections such as WAF rules specifically targeting SQL injection patterns related to these parameters. Monitor logs for unusual database queries or errors that could indicate exploitation attempts. Restrict access to the scheduling system to trusted networks or VPNs where possible. Plan for an upgrade or replacement of the vulnerable software version once a vendor patch is released. Additionally, conduct regular backups of scheduling data to enable recovery in case of data corruption or loss.

Description

A vulnerability has been found in code-projects Simple Scheduling System 1.0. Affected by this issue is some unknown functionality of the file /addtime.php. The manipulation of the argument starttime/endtime leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…