CVE-2026-10227
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 vulnerability has been found in raisulislamg4 student_management_system_by_php up to 310d950e09013d5133c6b9210aff9444382d16d1. The affected element is an unknown function of the file add_user_check.php of the component User Creation Handler. The manipulation of the argument role leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. 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 confidenceSQL injection vulnerability in the User Creation Handler of add_user_check.php where the 'role' parameter is not properly sanitized before being used in SQL queries. An attacker can manipulate the role argument to inject arbitrary SQL commands, potentially allowing unauthorized data access or manipulation of the user database.
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.
-
Locate the vulnerable PHP fileSearch the web root for add_user_check.php - common paths include /admin/, /user/, or /include/ directories. Use: find /var/www -name 'add_user_check.php' 2>/dev/nullAffected if The file exists in the application directory tree and is readable by the web server process
-
Verify the role parameter is processedExamine add_user_check.php and look for code handling the 'role' parameter - search for $_POST['role'], $_GET['role'], or Request::param('role') patternsAffected if The file processes a 'role' parameter without visible input sanitization or prepared statements
-
Confirm lack of parameterized queriesGrep the file for 'prepare', 'bindParam', 'bindValue', or 'execute' statements around the role parameter usage: grep -E '(prepare|bindParam|bindValue)' add_user_check.phpAffected if No prepared statement or parameter binding is found in the code handling the role parameter
-
Check if user creation is exposed without authenticationReview the file's authentication checks at the top - look for session_start(), isLoggedIn(), or auth middleware inclusions. If none exist before the SQL query, the endpoint is unauthenticatedAffected if No authentication check or session validation appears before the SQL operation on the role parameter
-
Test if the endpoint is accessible externallyAttempt a HEAD/GET request to the add_user_check.php endpoint from an unauthenticated context or check web server access logs for requests to this fileAffected if The endpoint responds to unauthenticated requests (HTTP 200 or other valid response rather than 401/403)
The environment is affected if add_user_check.php exists, processes a 'role' parameter without parameterized queries, and is accessible without authentication.
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 dynamic SQL queries with parameterized queries/prepared statements for the role parameter and all user input in add_user_check.php. Implement proper input validation and ensure the principle of least privilege for database connections.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10227 — 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-10227 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