CVE-2026-10620
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 flaw has been found in code-projects Student Admission System 1.0. Affected is an unknown function of the file /index.php. This manipulation of the argument eid/did causes sql injection. The attack is possible to be carried out remotely. The exploit has been published 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 confidenceSQL injection vulnerability in the Student Admission System 1.0 index.php file via the 'eid' or 'did' parameter, allowing remote attackers to inject malicious SQL queries.
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.
-
Confirm Student Admission System is installedLocate the web application directory and identify if the 'Student Admission System' application is present. Check for index.php, admission-related files, or application-specific directories in the web root.Affected if The application 'code-projects Student Admission System' is found on the server
-
Verify the installed version is 1.0Check version information in the application: look for version.php, about.php, README files, or any file containing '1.0' or 'version'. Compare the discovered version against the affected range.Affected if The installed version is 1.0 or falls within the affected version range
-
Locate the vulnerable /index.php fileFind the index.php file in the web application root directory. Verify it exists and is accessible as the main entry point.Affected if The file /index.php exists in the application directory
-
Inspect index.php for eid/did parameter usageOpen /index.php and search for occurrences of 'eid' or 'did' in the code. Identify where these parameters are received from user requests (via GET/POST).Affected if The eid or did parameters are present and used in the application code
-
Check for unsanitized SQL queriesReview the code around the eid/did parameter handling. Look for SQL query construction where these parameters are directly concatenated or inserted into query strings without using prepared statements, parameterized queries, or sanitization functions.Affected if User input from eid/did parameters is directly used in SQL queries without sanitization or parameterization
If Student Admission System version 1.0 is installed and the eid/did parameters in /index.php are used in SQL queries without sanitization, the environment is affected by this SQL injection vulnerability.
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 statements/prepared statements in index.php for the eid/did parameters to prevent SQL injection attacks.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10620 — 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-10620 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