/

CVE-2026-86210

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Class Exam Timetabling System

CVE-2026-86210

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Compromise and Unauthorized Data Manipulation

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A SQL injection vulnerability in the Class and Exam Timetabling System allows attacker-controlled input in the user-account deletion workflow to influence database queries. Because the affected endpoint is remotely reachable, an unauthenticated or otherwise unauthorized attacker may be able to manipulate database operations, depending on application access controls.

Affected context

The vulnerability occurs in the /delete_user_account.php endpoint of the Class and Exam Timetabling System 1.0 when the ID argument is incorporated into a database query without adequate parameterization or validation. Risk depends on whether the endpoint is exposed remotely, whether authentication is enforced, and what database privileges the application uses.

Exploit preconditions

  • Attack surface: The remotely accessible /delete_user_account.php endpoint
  • Required access: Ability to send requests to the affected endpoint; authentication requirements depend on deployment configuration
  • Trigger point: Processing of the ID argument during user-account deletion
  • Why exploitation is possible: Attacker-controlled input may be interpreted as part of a database statement rather than strictly as an identifier

Why this happens

The underlying bug is insufficient separation between user-supplied data and SQL command structure. If the ID argument is concatenated into a query or otherwise processed without parameterized statements and appropriate allowlist validation, crafted input can alter the query's intended meaning. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component.

Potential impact

  • Unauthorized deletion or modification of database records may occur
  • Sensitive application data could be disclosed
  • Database integrity could be undermined
  • Authentication or authorization data could be altered
  • The application or connected database service could become unavailable

General mitigation guidance

Mitigation generally centers on removing SQL syntax interpretation from request-controlled values and reducing the trust placed in endpoint input.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Validate identifiers using strict type and range allowlists before processing
  • Apply authorization checks at the server-side deletion operation
  • Use database accounts with only the privileges required by the application
  • Avoid exposing destructive endpoints without appropriate authentication and request protections
  • Return generic errors that do not disclose database details
  • Treat input validation as an additional control rather than a replacement for query parameterization

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules that identify string concatenation or interpolation in SQL statements
  • Code review checks for request parameters passed directly into database APIs
  • Dynamic testing of identifier parameters using non-destructive SQL injection test cases
  • Web application firewall policies that detect suspicious query-manipulation patterns
  • Database monitoring for unexpected query structures, repeated errors, or unauthorized destructive operations
  • Automated security review tools that flag unparameterized database access

Sources

SourceLink
github.comgithub.com/justconter/cve/issues/8
vuldb.comvuldb.com/cve/CVE-2026-86210
vuldb.comvuldb.com/submit/896590
vuldb.comvuldb.com/vuln/399345
vuldb.comvuldb.com/vuln/399345/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The affected functionality is exposed through a remotely reachable web endpoint, although practical exploitability depends on network exposure, authentication, and authorization controls.

The available description does not establish a specific authentication requirement. Access to the endpoint and its deletion functionality is the key condition, so deployments should verify both routing and authorization behavior.

Use parameterized queries for the deletion operation, validate the identifier as an expected data type, and enforce server-side authorization before performing the action.

Standardize secure database-access APIs, prohibit query construction through string concatenation, apply least-privilege database permissions, and include static analysis and authorized dynamic testing in development pipelines.

Find out what's already
exploitable in your codebase.