dbcve.org
Student File Management SystemApplication · Fabian

CVE-2025-14646

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 security flaw has been discovered in code-projects Student File Management System 1.0. This impacts an unknown function of the file /admin/delete_student.php. The manipulation of the argument stud_id results in sql injection. The attack may be performed from remote. The exploit has been released to the public and may be exploited.

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 Student File Management System 1.0 at /admin/delete_student.php. The 'stud_id' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. This is a critical flaw as it may allow unauthenticated remote attackers to exfiltrate, modify, or delete database contents.

MitigationImplement parameterized queries (prepared statements) for all database operations involving user input, particularly the stud_id parameter in delete_student.php. Validate and sanitize all inputs, apply least-privilege database accounts, and consider deploying a WAF as an additional layer of defense.

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 installed product and version
    Locate the application files and check for version indicators such as a version.txt file, footer text, or admin panel version display. Search for any file containing '1.0' as version information related to Fabian Student File Management System.
    Affected if The application is Fabian Student File Management System version 1.0
  2. Verify vulnerable file exists
    Check the web server document root for the presence of /admin/delete_student.php file. On Linux, run: find /var/www -name 'delete_student.php' 2>/dev/null or on Windows search for this file in the web directory.
    Affected if The file /admin/delete_student.php exists on the server
  3. Check if admin directory is network-exposed
    Attempt to access http://yourdomain/admin/ or http://yourdomain/delete_student.php from an external host or check server access logs for unauthenticated requests to /admin/ paths. Review web server configuration (Apache .htaccess, Nginx config) for access restrictions.
    Affected if The /admin/ directory is accessible without authentication from the network
  4. Review delete_student.php for direct parameter handling
    Open delete_student.php in a text editor and locate the code handling the 'stud_id' parameter. Search for SQL queries that use this parameter directly without prepared statements, parameterized queries, or input sanitization functions.
    Affected if The stud_id parameter is used directly in SQL queries without prepared statements or sanitization

You are affected if running Student File Management System 1.0 with the vulnerable /admin/delete_student.php file present and accessible, where the stud_id parameter is handled without parameterized queries.

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 involving user input, particularly the stud_id parameter in delete_student.php. Validate and sanitize all inputs, apply least-privilege database accounts, and consider deploying a WAF as an additional layer of defense.

Fix this in Student File Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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