dbcve.org
Online Student Result SystemApplication · Oretnom23

CVE-2025-11601

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-11
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 Result System 1.0. Affected by this vulnerability is an unknown functionality of the file /login.php. Performing manipulation of the argument Username results in sql injection. The attack can be initiated 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.php file of SourceCodester Online Student Result System 1.0. The Username parameter is not properly sanitized, allowing an attacker to inject malicious SQL queries. This can lead to unauthorized database access, authentication bypass, or data exfiltration.

MitigationImplement prepared statements/parameterized queries for all database operations, particularly in the login authentication logic. Validate and sanitize all user inputs before using them in SQL queries.

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 Result 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 if Oretnom23 Online Student Result System is installed
    Search the web server document root for files or directories containing keywords like 'student', 'result', 'ors', or check application deployment lists for this specific application
    Affected if The application is present on the server
  2. Verify the installed version is 1.0
    Check version.php, version.txt, or any version file in the application root directory, or look at the login page footer/source for version information
    Affected if The version is 1.0
  3. Confirm login.php exists in the application
    Check for the presence of login.php in the application root directory - typically found at /login.php or /admin/login.php
    Affected if login.php file exists in the application
  4. Verify the application is network accessible
    Confirm the login page is reachable via HTTP/HTTPS from a browser or curl request to the login.php endpoint
    Affected if The login page is accessible over the network

The environment is affected if the Oretnom23 Online Student Result System version 1.0 is installed and its login.php is accessible over the network, since the Username parameter in that file contains the SQL injection vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations, particularly in the login authentication logic. Validate and sanitize all user inputs before using them in SQL queries.

Recommended fix Moderate confidence
  1. 1. Replace the vulnerable SQL query in /login.php with a parameterized query (prepared statement) that separates code from data
  2. 2. For example, if using MySQLi, change from: $result = mysqli_query($conn, "SELECT * FROM users WHERE username='$username'") to: $stmt = $conn->prepare("SELECT * FROM users WHERE username = ?"); $stmt->bind_param("s", $username); $stmt->execute();
  3. 3. Alternatively, if using PDO: $stmt = $conn->prepare("SELECT * FROM users WHERE username = :username"); $stmt->bindParam(':username', $username); $stmt->execute();
  4. 4. Ensure all user input is validated and sanitized before use in any database queries
  5. 5. Apply the principle of least privilege to the database user account used by the application
  6. 6. As an interim mitigation, consider deploying a Web Application Firewall (WAF) to filter malicious SQL injection payloads
  7. 7. If the application is publicly accessible, temporarily restrict access to the login page until the patch is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Online Student Result System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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