dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4842

HIGH · 7.3 CVSS v3.1 Published 2026-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 security vulnerability has been detected in itsourcecode Online Enrollment System 1.0. This vulnerability affects unknown code of the file /sms/grades/index.php?view=edit&id=1 of the component Parameter Handler. The manipulation of the argument deptid leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may 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 itsourcecode Online Enrollment System 1.0 allows remote attackers to manipulate the deptid parameter in /sms/grades/index.php?view=edit&id=1, potentially executing arbitrary SQL commands against the database.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the deptid parameter, implement proper input validation, and apply output encoding. Consider deploying a WAF as a temporary compensating control until the code fix is implemented.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 application
    Check the application by visiting the homepage or checking deployed files for itsourcecode Online Enrollment System branding or identifying strings
    Affected if The application is itsourcecode Online Enrollment System
  2. Determine the installed version
    Check the application version by examining the source code, README files, or version information typically found in the web root or admin panel
    Affected if The version is 1.0 (or an unpatched version)
  3. Locate the vulnerable file
    Check if the file /sms/grades/index.php exists in the deployed web root directory
    Affected if The file exists and is accessible via the web server
  4. Verify the deptid parameter handling
    Inspect the source code of /sms/grades/index.php to determine if the deptid parameter is used in dynamic SQL queries without proper parameterization
    Affected if The deptid parameter is processed through direct SQL concatenation rather than prepared statements
  5. Confirm network exposure
    Determine if the application is accessible from external networks by checking firewall rules and web server configuration
    Affected if The application is reachable from remote networks without proper access restrictions

If the application is itsourcecode Online Enrollment System version 1.0 with the /sms/grades/index.php file present and accessible, and the deptid parameter is handled via dynamic SQL queries without prepared statements, then the environment is affected by CVE-2026-4842.

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 parameterized queries/prepared statements for the deptid parameter, implement proper input validation, and apply output encoding. Consider deploying a WAF as a temporary compensating control until the code fix is implemented.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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