dbcve.org
University Management SystemApplication · Angeljudesuarez

CVE-2026-3411

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-02
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 security vulnerability has been detected in itsourcecode University Management System 1.0. Affected by this issue is some unknown functionality of the file /admin_single_student_update.php. The manipulation of the argument ID leads to sql injection. Remote exploitation of the attack is possible. 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 · moderate confidence

SQL injection vulnerability in the ID parameter of /admin_single_student_update.php in itsourcecode University Management System 1.0 allows remote unauthenticated attackers to inject arbitrary SQL queries, potentially leading to full database compromise including student records and credentials.

MitigationImplement parameterized queries (prepared statements) for all database operations in the affected file and apply input validation/sanitization on the ID parameter. Until an official patch is available, consider restricting access to the /admin/ directory via network-level controls.

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
University Management 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. Locate the vulnerable PHP file
    Search the webroot for the file /admin_single_student_update.php using: find /var/www -name "admin_single_student_update.php" 2>/dev/null or dir /s /b C:\inetpub\wwwroot\admin_single_student_update.php
    Affected if The file exists in the web directory tree, indicating the affected application is installed
  2. Verify the application version
    Check for version indicators in the application - look for a version.php file, README, or footer/header files that may contain '1.0' or 'University Management System'
    Affected if Version is 1.0, matching the affected version range
  3. Inspect the ID parameter handling in the vulnerable file
    Open admin_single_student_update.php and examine how the 'id' parameter is used in database queries - search for $_GET['id'] or $_POST['id'] followed by direct SQL concatenation
    Affected if The ID parameter is used directly in SQL queries without prepared statements or parameter binding (e.g., no $stmt->prepare(), no mysqli_prepare(), no PDO::prepare())
  4. Check admin directory accessibility
    Attempt to access http://target/admin/ or http://target/admin_single_student_update.php directly without authentication
    Affected if The admin interface is accessible without login, allowing unauthenticated SQL injection attacks
  5. Verify database error handling exposes SQL errors
    Submit a crafted ID value like ' OR '1'='1 to the endpoint and observe if SQL error messages are returned in the response
    Affected if SQL errors or unexpected database output is returned, confirming the injection point is exploitable

The environment is affected if the University Management System 1.0 is installed with the admin_single_student_update.php file present and the ID parameter is handled without prepared statements in the code.

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

Implement parameterized queries (prepared statements) for all database operations in the affected file and apply input validation/sanitization on the ID parameter. Until an official patch is available, consider restricting access to the /admin/ directory via network-level controls.

Fix this in University Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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