dbcve.org
Online Student File Management SystemApplication · Janobe

CVE-2025-10593

HIGH · 8.8 CVSS v3.1 Published 2025-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 detected in SourceCodester Online Student File Management System 1.0. Affected is an unknown function of the file /admin/update_student.php. Performing manipulation of the argument stud_id results in sql injection. It is possible to initiate the attack remotely. The exploit is now public and may 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 · high confidence

SQL injection vulnerability in SourceCodester Online Student File Management System 1.0 allows remote attackers to inject malicious SQL queries via the stud_id parameter in /admin/update_student.php. The parameter is not properly sanitized or using parameterized queries, enabling database compromise.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries for the stud_id parameter and implement proper input validation before executing database 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
Online 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 the vulnerable PHP file
    Search for the file /admin/update_student.php in your web server's document root. Common paths include /var/www/html/, /www/, or C:\xampp\htdocs\. Use: find /var/www -name "update_student.php" 2>/dev/null
    Affected if The file exists in your web root and belongs to the Online Student File Management System
  2. Confirm the application version
    Check for a version file or header in the application. Look for version.php, README.txt, or check the main index.php for a version string. Compare against the affected version 1.0
    Affected if The installed version is exactly 1.0 (Janobe Online Student File Management System)
  3. Verify the stud_id parameter is processed
    Examine the code in /admin/update_student.php. Look for occurrences of $_GET['stud_id'] or $_POST['stud_id']. Search for direct usage of this parameter in SQL queries without sanitization functions like mysqli_real_escape_string or without prepared statements
    Affected if The stud_id parameter is used directly in SQL queries without proper escaping or parameterized queries
  4. Check if the admin interface is network accessible
    Determine if the /admin/ directory is accessible from the network. Test with: curl -I http://yourserver/admin/update_student.php. Also check if authentication is required and if the endpoint responds to requests
    Affected if The update_student.php endpoint is accessible without authentication or accessible to remote attackers who have admin credentials
  5. Inspect database query patterns
    Open /admin/update_student.php and search for SQL query construction. Look for patterns like: mysql_query, mysqli_query, or PDO::query where the stud_id variable is concatenated directly into the query string
    Affected if SQL queries involving stud_id are built by string concatenation rather than using prepared statements or parameter binding

You are affected if the Online Student File Management System version 1.0 is installed, the file /admin/update_student.php exists, and the stud_id parameter is handled in SQL queries without parameterized queries or input sanitization.

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 prepared statements/parameterized queries for the stud_id parameter and implement proper input validation before executing database operations.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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