dbcve.org
Scholars Tracking SystemApplication · Fabian

CVE-2025-14940

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-19
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 code-projects Scholars Tracking System 1.0. The affected element is an unknown function of the file /admin/delete_user.php. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack 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 Scholars Tracking System 1.0's /admin/delete_user.php file allows remote attackers to inject malicious SQL queries via the ID parameter. The critical CVSS 9.8 score indicates trivial exploitability with potential for complete database compromise, including exfiltration of sensitive scholar data.

MitigationImplement prepared statements/parameterized queries for all database operations in delete_user.php, audit similar files for additional SQL injection points, and consider deploying a WAF rule as an interim control until code-level fixes are validated.

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
Scholars Tracking 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 Fabian Scholars Tracking System is installed
    Locate the web application root directory. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\ depending on the server OS. Look for the Scholars Tracking System application files.
    Affected if The Fabian Scholars Tracking System application files are present on the server
  2. Verify the application version
    Check for a version file in the application root, or look for version information in the source code comments, README files, or admin interface. Compare the installed version to the affected version = 1.0.
    Affected if The installed version is Fabian Scholars Tracking System 1.0
  3. Verify the vulnerable file exists
    Check for the presence of /admin/delete_user.php in the web application directory. This file should exist within the application's admin folder.
    Affected if The file /admin/delete_user.php exists in the Scholars Tracking System installation
  4. Check if the admin interface is accessible
    Attempt to access the admin login page or the delete_user.php endpoint directly via HTTP/HTTPS. Determine if the application is publicly accessible or if the admin panel is exposed.
    Affected if The /admin/delete_user.php endpoint is reachable from the network being assessed
  5. Inspect the delete_user.php code for SQL injection vulnerability
    Open /admin/delete_user.php in a text editor. Locate the SQL query that uses the ID parameter. Check if the ID parameter is used directly in the SQL query without proper sanitization, prepared statements, or parameterized queries.
    Affected if The ID parameter is used in SQL queries without prepared statements, parameterized queries, or proper input sanitization

A user is affected if they have Fabian Scholars Tracking System version 1.0 installed with the vulnerable /admin/delete_user.php file and the ID parameter in that file is not protected against SQL injection.

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 prepared statements/parameterized queries for all database operations in delete_user.php, audit similar files for additional SQL injection points, and consider deploying a WAF rule as an interim control until code-level fixes are validated.

Fix this in Scholars Tracking 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-2025-14940 — 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-14940 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