dbcve.org
InjectionWeakness · CWE-74

CVE-2026-9474

HIGH · 7.3 CVSS v3.1 Published 2026-05-25
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 vulnerability was found in yashpokharna2555 StudentManagementSystem up to cb2f558ddf8d19396de0f92abf2d224d46a0a203. Affected by this issue is the function confirm_logged_in of the file /studentdel.php. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been made public and could be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

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

A SQL injection vulnerability exists in the StudentManagementSystem's /studentdel.php file, specifically in the confirm_logged_in function. The ID parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. The exploit has been publicly disclosed.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in studentdel.php, and implement proper input validation for the ID parameter. Apply input sanitization to the confirm_logged_in function.

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. Locate the vulnerable PHP file
    Search the web root directory for the file /studentdel.php using file system search commands (e.g., find, dir, or locate).
    Affected if The file studentdel.php exists in the web application directory structure.
  2. Verify the vulnerable function exists
    Open studentdel.php and search for the function definition 'function confirm_logged_in' within the file.
    Affected if The confirm_logged_in function is defined in studentdel.php.
  3. Check if ID parameter is used unsafely
    Within studentdel.php, locate where the ID parameter is processed (e.g., $_GET['ID'] or $_POST['ID']) and verify if it is directly concatenated into SQL queries without escaping, parameterized queries, or input validation.
    Affected if The ID parameter is directly interpolated into SQL strings without sanitization or prepared statements.
  4. Inspect SQL query patterns
    Search the file for SQL query patterns (SELECT, INSERT, UPDATE, DELETE) and examine whether they use the ID parameter. Look for signs of direct string concatenation like $sql = "..." . $_REQUEST['ID'] or similar constructs.
    Affected if SQL queries involving the ID parameter do not use parameterized queries (e.g., no $stmt->prepare() or mysqli_prepare()) and instead concatenate user input.
  5. Determine application version
    Check for version information in application metadata (composer.json, version files, headers, or admin panels) and compare against any official version ranges if available.
    Affected if The installed version cannot be confirmed as patched or is within an unpatched version range.

The environment is affected if studentdel.php exists with the confirm_logged_in function and the ID parameter is used in SQL queries without prepared statements or input sanitization.

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 in studentdel.php, and implement proper input validation for the ID parameter. Apply input sanitization to the confirm_logged_in function.

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-9474 — 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-9474 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