dbcve.org
Online Student Enrollment SystemApplication · Itsourcecode

CVE-2026-36233

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-10
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 SQL injection vulnerability was found in the assignInstructorSubjects.php file of itsourcecode Online Student Enrollment System v1.0. The reason for this issue is that attackers can inject malicious code via the parameter "subjcode" and use it directly in SQL queries without the need for appropriate cleaning 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 confidence

SQL injection vulnerability in itsourcecode Online Student Enrollment System v1.0 where the 'subjcode' parameter in assignInstructorSubjects.php is directly used in SQL queries without sanitization or parameterized queries, allowing attackers to manipulate database queries.

MitigationReplace direct SQL query construction with prepared statements/parameterized queries and implement proper input validation for the subjcode parameter.

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
Online Student Enrollment 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. Confirm the application is Itsourcecode Online Student Enrollment System
    Check your web server's document root for the presence of the Online Student Enrollment System. Look for files like index.php, login.php, or a folder structure consistent with this application. Verify the application name in the HTML source or README files if present.
    Affected if The application installed is Itsourcecode Online Student Enrollment System
  2. Verify the vulnerable file exists
    Locate assignInstructorSubjects.php in your web application directory. This file is typically found within the admin or instructor management modules of the system.
    Affected if assignInstructorSubjects.php exists in the application directory
  3. Inspect the file for direct SQL query usage
    Open assignInstructorSubjects.php and examine the code around the 'subjcode' parameter. Look for SQL query construction where $_POST['subjcode'] or $_GET['subjcode'] is directly concatenated into the query string without using prepared statements, mysqli_prepare, or PDO prepare methods.
    Affected if The code shows SQL queries that directly include the subjcode parameter without parameterized queries or input sanitization
  4. Confirm the application uses a database
    Verify that the system connects to a MySQL or MariaDB database by checking for database configuration files (such as db.php, config.php, or similar) and database connection code within the application.
    Affected if The application connects to a database and the vulnerable file handles subject-instructor assignments
  5. Check if the affected endpoint is accessible
    Determine if the assignInstructorSubjects.php file is accessible via web requests. Check if there are any access controls or authentication requirements that would limit access to this functionality.
    Affected if The endpoint is accessible (with or without authentication) and accepts user input for the subjcode parameter

You are affected if you are running Itsourcecode Online Student Enrollment System version 1.0 and the assignInstructorSubjects.php file exists with direct SQL query construction using the subjcode parameter.

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 direct SQL query construction with prepared statements/parameterized queries and implement proper input validation for the subjcode parameter.

Fix this in Online Student Enrollment System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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