dbcve.org
Student Management SystemApplication · Angeljudesuarez

CVE-2025-15168

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-29
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 identified in itsourcecode Student Management System 1.0. Affected is an unknown function of the file /statistical.php. Such manipulation of the argument ID leads to sql injection. The attack can be executed remotely. The exploit is publicly available and might 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 itsourcecode Student Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /statistical.php. The vulnerability is exploitable remotely with publicly available exploit code and carries a critical CVSS 9.8 rating.

MitigationImplement parameterized queries or prepared statements for all database interactions involving user input, specifically the ID parameter in /statistical.php. Alternatively, apply vendor patch if available.

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 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. Confirm Student Management System is installed
    Identify if the Angeljudesuarez Student Management System web application is present in your environment by reviewing deployed web applications, checking web server document roots, or enumerating installed web applications.
    Affected if The application is deployed and accessible on your server
  2. Verify the installed version is 1.0
    Check the application version by reviewing application files for version identifiers, checking about/pages in the application, or querying any version endpoint. Compare your installed version against the affected range: = 1.0
    Affected if The installed version is exactly 1.0
  3. Confirm statistical.php endpoint exists
    Locate and verify the presence of the /statistical.php file in the web application directory structure. Check web server access logs for requests to this endpoint.
    Affected if The file /statistical.php exists in the web application
  4. Check if ID parameter accepts user input without sanitization
    Review the source code of /statistical.php to determine if the ID parameter is used in SQL queries without proper parameterization, prepared statements, or input sanitization. Look for SQL queries that directly incorporate the ID parameter.
    Affected if The ID parameter is used in SQL queries without parameterized queries or input validation
  5. Assess network accessibility of the vulnerable endpoint
    Determine if the /statistical.php endpoint is exposed to network access, either internally or externally. Check firewall rules, network segmentation, and web server access controls.
    Affected if The endpoint is network-accessible without proper network-level restrictions

Your environment is affected if the Angeljudesuarez Student Management System version 1.0 is deployed with the /statistical.php endpoint accessible and the ID parameter used in unsanitized SQL 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 or prepared statements for all database interactions involving user input, specifically the ID parameter in /statistical.php. Alternatively, apply vendor patch if available.

Fix this in Student Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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