dbcve.org
Scholars Tracking SystemApplication · Fabian

CVE-2025-70152

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-18
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
code-projects Community Project Scholars Tracking System 1.0 is vulnerable to SQL Injection in the admin user management endpoints /admin/save_user.php and /admin/update_user.php. These endpoints lack authentication checks and directly concatenate user-supplied POST parameters (firstname, lastname, username, password, user_id) into SQL queries without validation or parameterization.

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

code-projects Community Project Scholars Tracking System 1.0 contains SQL Injection vulnerabilities in /admin/save_user.php and /admin/update_user.php. These endpoints accept POST parameters (firstname, lastname, username, password, user_id) and directly concatenate them into SQL queries without any input validation, sanitization, or parameterized queries, and lack authentication checks entirely.

MitigationImplement authentication checks on admin endpoints and replace direct string concatenation with prepared statements/parameterized queries for all SQL operations.

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. Locate Scholars Tracking System installation
    Search for the application web root directory (commonly in /var/www/html, /www/html, or C:\inetpub\wwwroot on Windows). Look for directories containing 'scholars', 'admin', or 'code-projects' in the name.
    Affected if The application directory contains the Scholars Tracking System (version 1.0) with the /admin/ folder present.
  2. Verify vulnerable PHP files exist
    Check for the presence of /admin/save_user.php and /admin/update_user.php within the application directory structure.
    Affected if Both files exist in the /admin/ directory of the application.
  3. Inspect save_user.php for SQL injection flaws
    Open /admin/save_user.php in a text editor or use 'grep -n "\$" save_user.php' to locate POST parameter handling ($firstname, $lastname, $username, $password). Look for direct SQL query construction using mysqli_query or mysql_query with concatenated variables.
    Affected if The file contains direct concatenation of POST parameters (firstname, lastname, username, password) into SQL queries without prepared statements or input sanitization.
  4. Inspect update_user.php for SQL injection flaws
    Open /admin/update_user.php and examine how the user_id and other POST parameters are handled in SQL queries. Search for patterns like mysqli_query($conn, "UPDATE..." . $variable).
    Affected if The file contains direct concatenation of user_id or other user-controlled input into UPDATE SQL statements without parameterization.
  5. Check for missing authentication on admin endpoints
    Review the beginning of both PHP files for session_start(), session_auth(), or any access control checks (such as checking if $_SESSION['user_id'] is set). Also test accessing the endpoints directly via curl or browser without providing credentials.
    Affected if Neither save_user.php nor update_user.php contain session validation or authentication checks at the start of the script.

If the Scholars Tracking System version 1.0 is installed with the /admin/ directory containing save_user.php and update_user.php that use direct SQL string concatenation without authentication, the environment is vulnerable to CVE-2025-70152.

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 authentication checks on admin endpoints and replace direct string concatenation with prepared statements/parameterized queries for all SQL operations.

Fix this in Scholars Tracking System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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