CVE-2025-11108
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 · uneditedA vulnerability was determined in code-projects Simple Scheduling System 1.0. Impacted is an unknown function of the file /schedulingsystem/addroom.php. Executing manipulation of the argument room can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.
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 · moderate confidenceSQL injection vulnerability in the Simple Scheduling System 1.0 allows remote attackers to inject malicious SQL queries via the 'room' parameter in /schedulingsystem/addroom.php. The lack of input sanitization or parameterized queries enables attackers to manipulate database queries, potentially achieving full database compromise including exfiltration or modification of sensitive data.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Simple Scheduling System is installedLocate the web application directory and identify if the Fabian Simple Scheduling System is present. Common paths include /var/www/html/schedulingsystem or C:\inetpub\wwwroot\schedulingsystem.Affected if The application directory contains the Simple Scheduling System files.
-
Verify the installed version is 1.0Check for a version file, readme.txt, or any documentation within the application directory that displays the version number. Compare against the affected version range.Affected if The installed version is exactly 1.0.
-
Locate the vulnerable file addroom.phpSearch for the file /schedulingsystem/addroom.php within the web application root directory and confirm it exists.Affected if The file addroom.php exists in the application.
-
Check if the 'room' parameter is processed without prepared statementsExamine the source code of addroom.php and look for SQL queries that incorporate the 'room' parameter directly. Search for patterns like 'INSERT INTO' or 'UPDATE' statements where $_POST['room'] or $_GET['room'] is concatenated directly into the query string rather than using parameterized queries or prepared statements.Affected if The 'room' parameter is used in SQL queries without parameterized queries or input sanitization.
A user is affected if they have the Simple Scheduling System version 1.0 installed with the addroom.php file accessible and the 'room' parameter processed in SQL queries without prepared statements.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries for all database interactions, particularly for the 'room' parameter in addroom.php; additionally, apply input validation and output encoding as defense-in-depth measures.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-11108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11108 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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