dbcve.org
Student Result ManagerApplication · Carmelo

CVE-2025-11551

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-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 vulnerability was determined in code-projects Student Result Manager 1.0. This affects an unknown function of the file src/students/Database.java. This manipulation of the argument roll/name/gpa causes sql injection. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.

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 critical SQL injection vulnerability exists in the Student Result Manager 1.0 application's Database.java file. User-controlled input for roll, name, and gpa parameters is directly concatenated into SQL queries without parameterization, allowing attackers to inject arbitrary SQL commands. This can lead to complete database compromise, including unauthorized access to sensitive student records, data exfiltration, or manipulation.

MitigationReplace dynamic SQL query construction with parameterized queries (PreparedStatement) in Database.java for all user-input fields (roll, name, gpa). Validate and sanitize all inputs, and apply the principle of least privilege to database accounts.

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 Result ManagerApplication
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 application version
    Locate the Student Result Manager application and identify its version number. Check application documentation, about page, or version file. The affected version is 1.0.
    Affected if The installed version is Carmelo Student Result Manager 1.0
  2. Locate vulnerable source file
    Find the file src/students/Database.java in the application installation directory or source code repository.
    Affected if The file src/students/Database.java exists in the application
  3. Check for dynamic SQL with roll parameter
    Open Database.java and search for SQL query strings that concatenate or embed the 'roll' parameter directly into queries without using PreparedStatement. Look for patterns like 'SELECT ... WHERE roll=' + roll or similar string concatenation.
    Affected if SQL queries use the 'roll' parameter via string concatenation or formatting rather than parameterized queries
  4. Check for dynamic SQL with name parameter
    In Database.java, search for SQL query strings that concatenate or embed the 'name' parameter directly into queries without PreparedStatement binding.
    Affected if SQL queries use the 'name' parameter via string concatenation or formatting rather than parameterized queries
  5. Check for dynamic SQL with gpa parameter
    In Database.java, search for SQL query strings that concatenate or embed the 'gpa' parameter directly into queries without PreparedStatement binding.
    Affected if SQL queries use the 'gpa' parameter via string concatenation or formatting rather than parameterized queries
  6. Verify PreparedStatement is not used for user inputs
    Confirm that the application does not use PreparedStatement with setString(), setInt(), or similar parameter binding methods for the roll, name, or gpa inputs in Database.java.
    Affected if User inputs (roll, name, gpa) reach SQL queries without PreparedStatement parameter binding

You are affected if you run Student Result Manager version 1.0 and the Database.java file contains dynamic SQL queries using string concatenation for roll, name, or gpa parameters instead of PreparedStatement parameterized 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

Replace dynamic SQL query construction with parameterized queries (PreparedStatement) in Database.java for all user-input fields (roll, name, gpa). Validate and sanitize all inputs, and apply the principle of least privilege to database accounts.

Fix this in Student Result Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA4.0 h
16.0 hours of engineering $2,850
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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