dbcve.org
Simple Scheduling SystemApplication · Fabian

CVE-2025-11115

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Simple Scheduling System 1.0's /addtime.php file allows remote attackers to inject malicious SQL queries through the starttime and endtime parameters without proper input sanitization. The critical CVSS score of 9.8 indicates trivial exploitation potential leading to full database compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the starttime and endtime parameters in addtime.php, and implement proper input validation to sanitize all user-supplied values before database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simple Scheduling SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Simple Scheduling System installation
    Search the web server filesystem for the 'addtime.php' file, typically found in the web root directory under a path like /var/www/html/ or similar web directory. Check for directories named 'scheduling', 'scheduler', or the application name.
    Affected if The addtime.php file exists in the web server's accessible directories.
  2. Verify the application version
    Check the application's source files for a version identifier. Common locations include a README file, version.php, or the main index.php header. Also check the HTTP response headers when accessing the application.
    Affected if The installed version is exactly 1.0, as this is the only affected version per the CVE.
  3. Inspect the vulnerable code in addtime.php
    Open the addtime.php file in a text editor or use 'grep' to search for the starttime and endtime parameters. Look for direct usage of these parameters in SQL queries without prepared statements or sanitization functions.
    Affected if The code contains SQL queries that directly incorporate $_POST or $_GET parameters for starttime/endtime without using parameterized queries.
  4. Confirm parameter handling without prepared statements
    Search the addtime.php file for patterns like '$starttime' or '$endtime' appearing inside SQL strings (using quotes) without being bound as parameters to mysqli_prepare or PDO::prepare. Use: grep -n 'starttime\|endtime' addtime.php
    Affected if The starttime and endtime parameters are concatenated directly into SQL strings rather than being passed as bound parameters.
  5. Test parameter accessibility
    If authorized for testing, send an HTTP POST request to addtime.php with test values in starttime and endtime parameters. Observe whether the application processes these without error or sanitization.
    Affected if The application accepts and processes the starttime and endtime parameters without rejecting special characters or SQL syntax.

The system is affected if Simple Scheduling System version 1.0 is installed and the addtime.php file exists with vulnerable SQL query handling for starttime/endtime parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements for the starttime and endtime parameters in addtime.php, and implement proper input validation to sanitize all user-supplied values before database queries.

Fix this in Simple Scheduling System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11115 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data