dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10225

HIGH · 7.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 raisulislamg4 student_management_system_by_php up to 310d950e09013d5133c6b9210aff9444382d16d1. This issue affects some unknown processing of the file login_check.php of the component Login. Performing a manipulation of the argument Username results in sql injection. The attack may be initiated remotely. The exploit is now public and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

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 the login_check.php component of student_management_system_by_php allows remote attackers to inject malicious SQL via the Username parameter. The attack is trivially exploitable as the vulnerable code directly incorporates user input into an SQL query without parameterization.

MitigationImplement prepared statements/parameterized queries for all SQL queries that incorporate user input, particularly in the login authentication logic. Until a fix is released, consider restricting network access to the application or implementing a WAF rule to block SQL injection payloads in the Username field.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Locate the login_check.php file
    Search the web server document root for the file login_check.php, typically found in the application root or an includes/admin folder of the student_management_system_by_php application
    Affected if The file exists and is accessible on the server
  2. Inspect SQL query construction in login_check.php
    Open login_check.php and examine the code that handles the login query. Look for SQL SELECT statements that include the Username parameter from $_POST or $_GET
    Affected if The Username parameter is directly concatenated into the SQL query string (e.g., $sql = "SELECT * FROM users WHERE username='" . $_POST['username'] . "'")
  3. Check for prepared statement usage
    Search the login_check.php file for PDO prepare(), mysqli_prepare(), or similar prepared statement functions
    Affected if No prepared statements or parameterized queries are used; the code relies on string concatenation to build SQL queries
  4. Verify lack of input sanitization
    Look for functions like mysqli_real_escape_string(), htmlspecialchars(), addslashes(), or input validation routines applied to the Username parameter before the SQL query
    Affected if The Username parameter is not sanitized or validated before being inserted into the SQL query
  5. Confirm the login form submits to login_check.php
    Find the login form HTML (typically in index.php or login.php) and verify it has an input field named 'username' that submits to login_check.php
    Affected if The login form passes the Username parameter directly to the vulnerable login_check.php script

A user is affected if the student_management_system_by_php application has a login_check.php file that uses direct string concatenation to insert the Username parameter into SQL queries without prepared statements or input 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.

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

Implement prepared statements/parameterized queries for all SQL queries that incorporate user input, particularly in the login authentication logic. Until a fix is released, consider restricting network access to the application or implementing a WAF rule to block SQL injection payloads in the Username field.

Recommended fix Moderate confidence
  1. Locate the login_check.php file in the student_management_system_by_php application
  2. Replace the vulnerable SQL query that directly incorporates the Username parameter with a prepared statement
  3. For example, change from: $sql = "SELECT * FROM users WHERE username='$username' AND password='$password'"
  4. To use parameterized queries: Use PDO or mysqli with prepared statements (e.g., $stmt = $pdo->prepare('SELECT * FROM users WHERE username = ?'); $stmt->execute([$username]);)
  5. Ensure input validation is also performed in addition to parameterized queries
  6. Test the login functionality to confirm the SQL injection vulnerability is remediated

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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