dbcve.org
Online Student File Management SystemApplication · Janobe

CVE-2025-10482

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
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 detected in SourceCodester Online Student File Management System 1.0. Affected is an unknown function of the file /admin/index.php. The manipulation of the argument Username results in sql injection. The attack can be executed 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

A SQL injection vulnerability exists in the login page (/admin/index.php) of SourceCodester Online Student File Management System 1.0. The Username parameter is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code. This can lead to authentication bypass, unauthorized access to administrative functions, and potential complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the Username parameter and all other user inputs. Apply input validation and ensure the database user follows least-privilege principles.

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
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. Verify the installed version of the file management system
    Check the application documentation, about page, or source code headers for version number 1.0. If the application was downloaded from SourceCodester, the filename or README typically indicates version 1.0.
    Affected if The installed version is confirmed as 1.0 of SourceCodester Online Student File Management System (also marketed as Janobe).
  2. Confirm the presence of the vulnerable login endpoint
    Locate and verify that the file /admin/index.php exists in the web root or admin directory of the deployed application.
    Affected if The file /admin/index.php exists and is accessible.
  3. Inspect the login processing code for SQL query construction
    Open /admin/index.php (or the file containing the login logic) and examine the PHP code that handles the Username parameter. Look for SQL queries where the username is concatenated or inserted directly into the query string without using prepared statements or parameter binding.
    Affected if The code contains SQL queries that directly embed the $_POST['username'] or similar user input into the query string without escaping, binding, or parameterized queries.
  4. Check for proper input sanitization or prepared statements
    Search the login processing code for functions like mysqli_prepare, PDO::prepare, or other parameterized query methods. Also check for sanitize functions applied to the username input before database use.
    Affected if No prepared statements or parameter binding are used for the username field, and no visible input validation/sanitization function is applied before the SQL query execution.

You are affected if you are running version 1.0 of this file management system, the /admin/index.php login page exists, and the source code shows direct embedding of the Username parameter into SQL queries without prepared statements or proper 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 parameterized queries (prepared statements) for the Username parameter and all other user inputs. Apply input validation and ensure the database user follows least-privilege principles.

Fix this in Online Student File Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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