dbcve.org
Student Management SystemApplication · Angeljudesuarez

CVE-2025-14334

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
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 flaw has been found in itsourcecode Student Management System 1.0. Affected is an unknown function of the file /new_adviser.php. Executing manipulation of the argument Name can lead to sql injection. The attack may be performed from remote. The exploit has been published 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

The itsourcecode Student Management System 1.0 is vulnerable to SQL injection via the Name parameter in /new_adviser.php. User-supplied input is not properly sanitized or parameterized before being used in SQL queries, allowing remote attackers to inject malicious SQL statements.

MitigationImplement prepared statements/parameterized queries for all database operations in new_adviser.php, or use a proper database abstraction layer with input validation on the Name parameter.

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. Identify the installed Student Management System version
    Locate the application directory and check version files, readme, or any version identifier within the itsourcecode/Angeljudesuarez Student Management System codebase. Compare against version 1.0.
    Affected if The installed version is 1.0 of the Angeljudesuarez Student Management System.
  2. Verify the vulnerable PHP file exists
    Check for the presence of the file new_adviser.php in the web root or application directory. Common paths may include /new_adviser.php or /admin/new_adviser.php.
    Affected if The file new_adviser.php exists in the application.
  3. Inspect the new_adviser.php source code for the Name parameter handling
    Open new_adviser.php and locate the code handling the 'Name' POST or GET parameter. Look for SQL query construction where the Name input is directly concatenated or inserted into the query string without using prepared statements, parameterized queries, or proper escaping functions.
    Affected if The Name parameter is used directly in an SQL query without prepared statements or input sanitization.
  4. Check if the application database uses a database abstraction layer with input validation
    Review the new_adviser.php file and any included database connection files to determine if database queries use a framework or abstraction layer that implements input validation or parameterized queries for the Name parameter.
    Affected if No prepared statements, parameterized queries, or input validation is implemented for the Name parameter in database operations.
  5. Confirm the web server exposes the vulnerable endpoint
    Verify the new_adviser.php file is accessible via the web server and accepts user input through GET or POST requests for the Name parameter.
    Affected if The new_adviser.php endpoint is accessible and processes user input for the Name parameter.

A user is affected if they are running version 1.0 of the Student Management System and the new_adviser.php file processes the Name parameter without prepared statements or input sanitization in 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 prepared statements/parameterized queries for all database operations in new_adviser.php, or use a proper database abstraction layer with input validation on the Name parameter.

Fix this in Student Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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