CVE-2026-9470
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 · uneditedA security vulnerability has been detected in yashpokharna2555 StudentManagementSystem cb2f558ddf8d19396de0f92abf2d224d46a0a203. This affects the function confirm_logged_in of the file student_trans.php. Such manipulation of the argument FIRST_NAME/Last_Name/EMAIL leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are 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 · moderate confidenceSQL injection vulnerability in StudentManagementSystem's student_trans.php file within the confirm_logged_in function. User-supplied input to FIRST_NAME, Last_Name, and EMAIL parameters is directly concatenated into SQL queries without proper sanitization or parameterized queries, allowing attackers to manipulate SQL statements remotely.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify StudentManagementSystem installationSearch for the student_trans.php file in your web server directories, typically under web root or application directories.Affected if The file student_trans.php exists in your environment
-
Locate the confirm_logged_in functionOpen student_trans.php and search for the function definition 'function confirm_logged_in' or 'function confirm_logged_in()'.Affected if The confirm_logged_in function is present in student_trans.php
-
Check for FIRST_NAME, Last_Name, EMAIL parameter handlingWithin the confirm_logged_in function, search for occurrences of FIRST_NAME, Last_Name, or EMAIL variables being used in SQL query strings.Affected if These parameters are used directly in SQL query strings without visible sanitization
-
Verify lack of input sanitizationInspect the code around these parameters for functions like mysqli_real_escape_string, prepared statements, parameter binding, or any input validation/filtering.Affected if No sanitization functions or prepared statements are used before incorporating these parameters into SQL queries
-
Confirm the application uses a databaseCheck if the file connects to a MySQL/MariaDB database and executes queries using these unsanitized parameters.Affected if The application executes SQL queries with the affected parameters against a database
Your environment is affected if StudentManagementSystem is installed with student_trans.php containing the confirm_logged_in function that processes FIRST_NAME, Last_Name, or EMAIL parameters in SQL queries without sanitization or prepared statements.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace direct SQL string concatenation with prepared statements/parameterized queries for all user inputs in the confirm_logged_in function. Implement input validation and output encoding as defense-in-depth measures.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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