dbcve.org
Student Management SystemApplication · Angeljudesuarez

CVE-2025-14644

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-14
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 vulnerability was determined in itsourcecode Student Management System 1.0. The impacted element is an unknown function of the file /update_subject.php. Executing manipulation of the argument ID can lead to sql injection. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.

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 itsourcecode Student Management System 1.0 in the /update_subject.php file allows remote attackers to manipulate the ID parameter to inject arbitrary SQL commands into the database query.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in update_subject.php, implement strict input validation on the ID parameter, and apply principle of least privilege to database accounts.

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
Student 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. Confirm Student Management System installation
    Locate the web application directory and identify if Angeljudesuarez Student Management System version 1.0 is deployed. Check for the presence of PHP files typical to this application structure.
    Affected if The application directory contains Student Management System files and the version cannot be determined or is confirmed as 1.0
  2. Verify vulnerable file exists
    Check for the presence of update_subject.php in the web application root or admin/subject directory. This file is required for the vulnerability to be present.
    Affected if The file update_subject.php exists in the application directory
  3. Check ID parameter exposure
    Examine the update_subject.php code to confirm it processes an ID parameter in the query string or POST data without sanitization, and that this parameter reaches the database query.
    Affected if The code shows direct use of $_GET['id'] or $_POST['id'] in SQL queries without parameterized statements or input validation
  4. Assess network accessibility
    Determine if the update_subject.php endpoint is accessible to remote users over HTTP/HTTPS. Check if authentication is required or if the page is publicly exposed.
    Affected if The vulnerable endpoint is accessible without authentication or from untrusted networks
  5. Review database configuration
    Check database user permissions configured for the web application. Determine if the database account has privileges beyond what the application requires for normal operation.
    Affected if The database user has elevated privileges (DROP, CREATE, or administrative access) that could be exploited via SQL injection

The environment is affected if Angeljudesuarez Student Management System 1.0 is deployed with the update_subject.php file accessible and the ID parameter processed in SQL queries without parameterization.

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 update_subject.php, implement strict input validation on the ID parameter, and apply principle of least privilege to database accounts.

Fix this in Student Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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