dbcve.org
Student File Management SystemApplication · Fabian

CVE-2025-14619

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-13
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 found in code-projects Student File Management System 1.0. Affected by this vulnerability is an unknown functionality of the file login_query.php. Performing manipulation of the argument stud_no results in sql injection. The attack may be initiated remotely. The exploit has been made public and could 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 Student File Management System 1.0's login_query.php script. The stud_no parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL commands. This is a critical authentication-related flaw with public exploit availability.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the stud_no parameter and implement proper input validation. Apply least-privilege database accounts and conduct thorough penetration testing post-remediation.

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 File 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. Identify if Student File Management System is installed
    Search the web server document root for files named 'login_query.php', 'student.php', or directories containing 'student' or 'file_management' in the name. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\
    Affected if The application directory or login_query.php file is found on the server
  2. Confirm the installed version is 1.0
    Look for a version file, readme.txt, or check the header/comments in login_query.php for version strings. Check any about.php, info.php, or config files for version metadata
    Affected if The version is explicitly listed as 1.0 or no version is found (indicating it may be the unpatched 1.0 release)
  3. Locate the vulnerable login_query.php script
    Navigate to the identified application directory and verify the presence of login_query.php. Open the file and search for the 'stud_no' parameter handling
    Affected if The file login_query.php exists and contains code handling the stud_no parameter
  4. Check if stud_no parameter uses unparameterized SQL queries
    Examine login_query.php source code. Search for SQL queries (SELECT, INSERT, UPDATE, DELETE) that directly incorporate the stud_no parameter without using prepared statements, parameterized queries, or escaping functions
    Affected if The code builds SQL queries by concatenating or interpolating the stud_no parameter directly into the query string without sanitization
  5. Verify the login functionality is accessible
    Confirm the login page that uses login_query.php is accessible via HTTP/HTTPS. Attempt to access the login URL directly or identify it through the application's entry points
    Affected if The login function is exposed and accepts user input via the stud_no parameter

A user is affected if Student File Management System version 1.0 is installed with the login_query.php file present and the stud_no parameter is handled via direct SQL string concatenation rather than prepared statements.

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 stud_no parameter and implement proper input validation. Apply least-privilege database accounts and conduct thorough penetration testing post-remediation.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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