CVE-2026-36235
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 SQL injection vulnerability was found in the scheduleSubList.php file of itsourcecode Online Student Enrollment System v1.0. The reason for this issue is that the 'subjcode' parameter is directly embedded into the SQL query via string interpolation without any sanitization or validation.
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 confidenceA SQL injection vulnerability exists in scheduleSubList.php of itsourcecode Online Student Enrollment System v1.0 where the 'subjcode' parameter is directly embedded into SQL queries via string interpolation without any sanitization or validation, allowing unauthenticated attackers to inject arbitrary SQL commands.
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.
-
Identify the application versionLocate and inspect the Itsourcecode Online Student Enrollment System installation files to confirm version 1.0. Check for version files, readme files, or admin panels that display the software version.Affected if The installed version is 1.0 of Itsourcecode Online Student Enrollment System
-
Locate scheduleSubList.phpSearch the web root directory for the file scheduleSubList.php. Common paths may include /admin/, /classes/, or similar application directories.Affected if The file scheduleSubList.php exists in the application directory
-
Inspect the subjcode parameter handlingOpen scheduleSubList.php and search for occurrences of 'subjcode' within SQL query strings. Look for patterns where $_GET['subjcode'] or $_POST['subjcode'] is directly concatenated into SQL statements.Affected if The file contains SQL queries that directly embed the 'subjcode' parameter without using prepared statements or parameter binding
-
Check for SQL injection vulnerability patternExamine the code around the 'subjcode' usage to confirm it uses string interpolation (like $sql = "SELECT ... WHERE subjcode = '$subjcode'") rather than parameterized queries (like $stmt->prepare with placeholders).Affected if The SQL code uses direct string interpolation or concatenation with the 'subjcode' parameter value
If you are running Itsourcecode Online Student Enrollment System v1.0 and scheduleSubList.php contains SQL queries that directly embed the 'subjcode' parameter via string interpolation, your environment is affected by this SQL injection vulnerability.
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 dataReplace direct string interpolation with parameterized queries (prepared statements) and implement proper input validation for the 'subjcode' parameter.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36235 — 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-2026-36235 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