/

CVE-2026-14642

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Class Timetabling System

CVE-2026-14642

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Data compromise and potential authentication bypass

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 flaw in the Class and Exam Timetabling System allows attackers to manipulate the ID parameter in edit_class2.php and inject arbitrary SQL queries.

When the application builds database statements directly from untrusted input, an attacker can remotely read, modify, or delete data and potentially escalate their access.

Affected context

The vulnerability occurs within the web-based Class and Exam Timetabling System when handling requests to edit_class2.php that include the ID parameter.

It typically manifests in deployments where user-supplied identifiers are concatenated into SQL statements without robust parameterization or encoding.

Any reachable instance of this script exposed to remote users, such as an internet-facing or intranet web server, may be affected depending on configuration and database privileges.

Exploit preconditions

  • Attack surface: HTTP requests to the edit_class2.php endpoint.
  • Required access: Network access to the web application; no special privileges if the endpoint is publicly reachable.
  • Trigger point: Supplying crafted values in the ID parameter that are processed into SQL queries.
  • Why exploitation is possible: The application appears to construct SQL statements by directly embedding the ID parameter without using prepared statements, proper escaping, or centralized query building controls.

Why this happens

The underlying issue aligns with CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') and CWE-74: Improper Neutralization of Special Elements in Output.

The application treats the ID parameter as trusted and interpolates it into SQL commands, allowing control characters and query fragments to alter the intended database operation.

This pattern reflects a broader bug class where business logic relies on dynamically built queries instead of parameterized statements, and where there is no strict separation between data and executable query syntax.

Potential impact

  • Attackers may read sensitive data from class, exam, and user-related tables.
  • Malicious users could modify or delete timetable and configuration records, disrupting operations.
  • SQL injection can potentially be used to bypass authentication or escalate privileges within the application.
  • Depending on database configuration, attackers might execute administrative commands or pivot to other applications sharing the same database.

General mitigation guidance

Mitigation generally focuses on enforcing strict separation between user input and query logic.

Common defensive patterns include using parameterized queries or ORM query builders rather than string concatenation, centralizing database access with vetted APIs, and validating identifiers and input types before use.

Additional safeguards involve applying least-privilege roles at the database level so that the web application account cannot perform high-risk operations, and adopting secure-by-default coding guidelines that prohibit dynamic SQL construction from raw request parameters.

How teams detect issues like this

Detection often relies on reviewing code paths that construct SQL statements from request parameters, especially for files like edit_class2.php that process identifiers.

Static analysis rules can flag concatenation of HTTP parameters into SQL strings and highlight missing prepared statements or query parameter binding.

Security-focused code review should look for custom query-building helpers, absence of centralized data access layers, and ad-hoc SQL fragments in controllers or views.

Organizations may also enforce policies that require automated scanning for injection patterns in pull requests and periodic dynamic testing with safe fuzzing of input parameters.

Sources

SourceLink
github.comgithub.com/sunjingyuan123/ccvvee/issues/1
vuldb.comvuldb.com/cve/CVE-2026-14642
vuldb.comvuldb.com/submit/846144
vuldb.comvuldb.com/vuln/376158
vuldb.comvuldb.com/vuln/376158/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

If the edit_class2.php endpoint is reachable over the network and not access-controlled, any remote user who can send requests to it may be able to exploit the SQL injection.

Only network access to the application is required; no local access to the server or database is necessary if the vulnerable script is publicly accessible.

Replace dynamic SQL construction with parameterized queries or ORM-based data access, validate and constrain the ID parameter to expected formats (such as numeric-only), and ensure database accounts operate with minimal privileges.

Adopt secure coding standards that forbid building SQL with string concatenation, integrate static analysis checks for injection vulnerabilities into CI pipelines, and perform regular security-focused code reviews for all database interaction layers.

Find out what's already
exploitable in your codebase.