dbcve.org
Online Student Enrollment SystemApplication · Itsourcecode

CVE-2026-36232

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 instructorClasses.php file of itsourcecode Online Student Enrollment System v1.0. The reason for this issue is that the 'classId' parameter from $_GET['classId'] is directly concatenated into the SQL query 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 confidence

SQL injection vulnerability in instructorClasses.php of itsourcecode Online Student Enrollment System v1.0 where the classId parameter from $_GET is directly concatenated into SQL queries without sanitization or validation, allowing arbitrary SQL command execution.

MitigationReplace direct SQL concatenation with prepared statements/parameterized queries and implement proper input validation for the classId parameter before use in any SQL query.

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. Identify the installed version of the enrollment system
    Locate the application files or check the application banner/footer for version information. Compare against version 1.0.
    Affected if The installed version is Itsourcecode Online Student Enrollment System version 1.0.
  2. Locate the instructorClasses.php file
    Search the web root directory for the file instructorClasses.php, typically found in admin or instructor-related directories.
    Affected if The file instructorClasses.php exists in the application web directory.
  3. Inspect the SQL query construction in instructorClasses.php
    Open instructorClasses.php and search for SQL query strings that include the 'classId' parameter via $_GET. Look for patterns where $_GET['classId'] is directly concatenated into a query string without using prepared statements or parameter binding.
    Affected if The code shows direct concatenation of the classId GET parameter into an SQL query string.
  4. Verify the classId parameter is received via GET request
    Check if the file uses $_GET['classId'] or $_REQUEST['classId'] to capture the parameter without sanitization functions such as mysqli_real_escape_string, htmlspecialchars, or parameter validation logic.
    Affected if The classId parameter is retrieved via GET and passed directly to the SQL query without sanitization.
  5. Test for SQL injection vulnerability (passive observation)
    Send a request to instructorClasses.php with a modified classId parameter (e.g., classId=1' OR '1'='1) and observe if the application returns database errors or unusual behavior. Use only safe, read-only test values that do not modify data.
    Affected if The application returns SQL syntax errors or unexpected database results when special characters are submitted in the classId parameter.

Your environment is affected if you are running Itsourcecode Online Student Enrollment System v1.0 and the instructorClasses.php file contains direct SQL concatenation with the unsanitized classId GET 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 concatenation with prepared statements/parameterized queries and implement proper input validation for the classId parameter before use in any SQL query.

Fix this in Online Student Enrollment System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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