dbcve.org
Simple Scheduling SystemApplication · Fabian

CVE-2025-11107

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 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.

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 allows remote attackers to manipulate the 'corcode' parameter in /schedulingsystem/addcourse.php to inject arbitrary SQL queries. The lack of input sanitization or parameterized queries enables complete database compromise.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries in addcourse.php, perform input validation on all user-supplied parameters, and apply least-privilege database access controls. A WAF can serve as an interim protective measure.

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. Verify Fabian Simple Scheduling System installation
    Look for the application in the web root directory. Common paths include /schedulingsystem/, /scheduling/, or under /var/www/, /htdocs/, or C:\inetpub\wwwroot\. Check for files like addcourse.php, index.php, or any scheduling-related application files.
    Affected if The application directory and its PHP files (particularly addcourse.php) are present on the server.
  2. Confirm the exact version installed
    Examine any version file, README, or header comments in the main PHP files. Look for version indicators in the source code such as 'version 1.0', '$version = "1.0"', or similar. Also check composer.json, package.json, or any config file that states the version.
    Affected if The installed version is exactly 1.0 (the only affected version per the CVE).
  3. Locate the vulnerable file
    Find /schedulingsystem/addcourse.php in the web application directory. Verify the file exists and is accessible via the web server.
    Affected if The file addcourse.php exists in the expected path.
  4. Examine SQL query handling in addcourse.php
    Open addcourse.php and search for any SQL query construction that uses the 'corcode' parameter. Look for patterns like $_POST['corcode'] or $_GET['corcode'] being concatenated directly into SQL strings (e.g., SELECT * FROM ... WHERE corcode = '" . $_POST['corcode'] . "'). Also search for mysqli_query(), mysql_query(), or PDO::query() calls without prepared statements.
    Affected if The 'corcode' parameter is used in SQL queries without parameterized queries, prepared statements, or input sanitization functions.
  5. Test if the parameter is exposed and controllable
    Check if addcourse.php processes GET or POST requests and accepts the 'corcode' parameter. Review the code to confirm the parameter flows from user input ($_REQUEST, $_GET, $_POST) into the SQL query without validation.
    Affected if The 'corcode' parameter is accepted as user input and passed directly into a dynamic SQL query.

If the Fabian Simple Scheduling System version 1.0 is installed and the file /schedulingsystem/addcourse.php exists with the 'corcode' parameter being used in unsanitized SQL queries, the environment is affected by CVE-2025-11107.

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 prepared statements/parameterized queries in addcourse.php, perform input validation on all user-supplied parameters, and apply least-privilege database access controls. A WAF can serve as an interim protective measure.

Fix this in Simple Scheduling System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11107 — 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-11107 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