dbcve.org
Simple Student Alumni SystemApplication · Carmelo

CVE-2026-26695

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-02
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
code-projects Simple Student Alumni System v1.0 is vulnerable to SQL Injection in /TracerStudy/recordstudent_edit.php.

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 confidence

code-projects Simple Student Alumni System v1.0 contains a SQL Injection vulnerability in /TracerStudy/recordstudent_edit.php. The vulnerability allows remote attackers to inject arbitrary SQL commands through unsanitized input parameters in the student record edit functionality, potentially enabling unauthorized database access, data theft, or complete system compromise.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) in recordstudent_edit.php and implement proper input validation on all user-supplied parameters.

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
Simple Student Alumni SystemApplication
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. Locate the vulnerable PHP file
    Search the web server document root for the file path /TracerStudy/recordstudent_edit.php or check if the TracerStudy directory exists in the application installation folder
    Affected if The file /TracerStudy/recordstudent_edit.php exists on the server and is accessible via the web application
  2. Confirm the application version
    Check the application source files for version identification markers (such as version comments in PHP files, README files, or version info in the source code). The affected version is 1.0.
    Affected if The installed version of Simple Student Alumni System is exactly 1.0
  3. Verify the web server exposes the application
    Confirm that the application is accessible over HTTP/HTTPS. Attempt to access the TracerStudy directory or recordstudent_edit.php endpoint via the web server.
    Affected if The vulnerable file is reachable through the web server (not restricted by authentication or network filters)
  4. Inspect the vulnerable code for SQL query patterns
    Open /TracerStudy/recordstudent_edit.php in a text editor and search for SQL query construction patterns. Look for direct concatenation of user input into SQL statements (e.g., SELECT, INSERT, UPDATE queries built with string concatenation or without prepared statements).
    Affected if The file contains SQL queries where user-supplied parameters from $_GET, $_POST, or similar sources are directly concatenated into query strings without parameterization
  5. Check input handling in the edit student record functionality
    Review the recordstudent_edit.php code to see how it handles the id or other parameters used to identify which student record to edit. Look for lack of sanitization, escaping, or use of prepared statements.
    Affected if The student record edit functionality processes input parameters without proper sanitization or uses dynamic SQL construction

The environment is affected if the Simple Student Alumni System version 1.0 is installed, the file /TracerStudy/recordstudent_edit.php exists and is web-accessible, and the code uses unsanitized input in SQL 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 queries with parameterized queries (prepared statements) in recordstudent_edit.php and implement proper input validation on all user-supplied parameters.

Fix this in Simple Student Alumni System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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