Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11116: SQL Injection in code-projects Simple Scheduling System

0
Medium
VulnerabilityCVE-2025-11116cvecve-2025-11116
Published: Sun Sep 28 2025 (09/28/2025, 19:02:05 UTC)
Source: CVE Database V5
Vendor/Project: code-projects
Product: Simple Scheduling System

Description

A vulnerability was found in code-projects Simple Scheduling System 1.0. This affects an unknown part of the file /add.home.php. The manipulation of the argument faculty results in sql injection. The attack can be executed remotely. The exploit has been made public and could be used. Other parameters might be affected as well.

AI-Powered Analysis

AILast updated: 10/06/2025, 00:43:26 UTC

Technical Analysis

CVE-2025-11116 is a SQL injection vulnerability identified in the Simple Scheduling System version 1.0 developed by code-projects. The vulnerability resides in the /add.home.php script, where the 'faculty' parameter is improperly sanitized, allowing remote attackers to inject arbitrary SQL commands. This injection flaw does not require authentication, user interaction, or elevated privileges, making it remotely exploitable over the network. The vulnerability can lead to unauthorized access to database contents, modification of data, or disruption of service depending on the injected payload. The CVSS 4.0 score is 6.9 (medium severity), reflecting the network attack vector, low complexity, no privileges or user interaction needed, and partial impact on confidentiality, integrity, and availability. Although the exact extent of affected parameters beyond 'faculty' is unknown, the presence of other vulnerable inputs is possible. No official patches or fixes have been published yet, and while the exploit code is publicly available, no confirmed active exploitation has been reported. This vulnerability poses a significant risk to organizations relying on this scheduling system for managing academic or organizational schedules, potentially exposing sensitive scheduling data or enabling further attacks through database compromise.

Potential Impact

For European organizations using the Simple Scheduling System 1.0, this vulnerability could lead to unauthorized disclosure of sensitive scheduling information, manipulation of scheduling data, or denial of service through database corruption. Confidentiality impacts include exposure of personal or institutional data stored in the database. Integrity impacts involve unauthorized modification or deletion of scheduling records, which could disrupt organizational operations. Availability could be affected if attackers execute commands that degrade or crash the database service. Given the unauthenticated remote exploitability, attackers can leverage this vulnerability to gain a foothold in the network or pivot to other systems. The impact is particularly critical for educational institutions, government agencies, or enterprises relying on this system for operational scheduling. The lack of patches increases the risk window, necessitating immediate mitigation efforts. Additionally, the public availability of exploit code raises the likelihood of opportunistic attacks targeting vulnerable deployments in Europe.

Mitigation Recommendations

Organizations should immediately implement input validation and sanitization for the 'faculty' parameter and any other user-supplied inputs in the /add.home.php script. Employing parameterized queries or prepared statements is essential to prevent SQL injection. If source code modification is not feasible, deploying Web Application Firewalls (WAFs) with rules to detect and block SQL injection patterns targeting the affected endpoint can provide temporary protection. Network segmentation and restricting access to the scheduling system to trusted internal users can reduce exposure. Monitoring database logs and web server logs for suspicious queries or unusual activity related to the 'faculty' parameter is recommended. Organizations should also track vendor communications for official patches or updates and plan for timely application once available. Conducting a thorough audit of all input parameters in the application for similar injection flaws is advisable. Finally, educating developers and administrators on secure coding practices will help prevent recurrence.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-27T17:37:37.693Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68d987277554179dcb262790

Added to database: 9/28/2025, 7:06:15 PM

Last enriched: 10/6/2025, 12:43:26 AM

Last updated: 12/28/2025, 6:55:27 AM

Views: 119

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats