/

CVE-2026-75080

Severity:

HIGH RISK

(7.3)

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

CVE-2026-75080

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized database access and 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 ID parameter of /edit_subject1.php to influence database queries.

Because the affected endpoint is remotely reachable, an attacker may be able to access, alter, or interfere with database information without authorization.

Affected context

The issue appears in the subject-editing functionality of SourceCodester Class and Exam Timetabling System 1.0, specifically while processing the ID argument submitted to /edit_subject1.php. Risk exists where externally supplied values reach database query construction without sufficient parameterization or validation.

Exploit preconditions

  • Attack surface: Remotely accessible web endpoint
  • Required access: Ability to send requests to the subject-editing functionality; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the ID parameter by /edit_subject1.php
  • Why exploitation is possible: Input may be incorporated into a database query without being safely separated from SQL syntax

Why this happens

The underlying bug is an injection flaw in which application-controlled and user-controlled data are not reliably separated during SQL query construction. If the ID value is concatenated into a query or otherwise interpreted as SQL syntax, crafted input can change the query's intended meaning. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and relates to the broader injection category represented by CWE-74.

Potential impact

  • An attacker may retrieve unauthorized database records
  • An attacker could modify or delete application data
  • Database integrity and timetable information may be compromised
  • The application may experience errors or service disruption
  • Exposed database credentials or privileges could increase downstream impact

General mitigation guidance

Mitigation generally focuses on ensuring that database commands treat request values strictly as data.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Apply allowlist-based validation and appropriate type handling for identifier fields
  • Avoid dynamically concatenating request values into SQL statements
  • Restrict database accounts to the minimum privileges required by the application
  • Centralize query construction and enforce secure data-access conventions
  • Add authorization checks around subject-editing operations and sensitive records
  • Reduce trust in client-supplied identifiers by verifying resource ownership and scope server-side

How teams detect issues like this

Organizations can identify SQL injection risks through:

  • Static analysis rules that flag string concatenation or formatting used to build SQL queries
  • Code review checks for request parameters reaching database APIs without binding
  • Dynamic testing of externally reachable parameters using controlled, non-destructive test inputs
  • Web application firewall or API policy rules monitoring anomalous database-oriented input patterns
  • Logging and alerting for unusual query errors, enumeration behavior, or unexpected access to records

Automated code review and software composition tools may help surface unsafe data-access patterns, but findings should be validated against application behavior.

Sources

SourceLink
github.comgithub.com/i-QvQ-i/first-OvO/issues/7
vuldb.comvuldb.com/cve/CVE-2026-75080
vuldb.comvuldb.com/submit/876546
vuldb.comvuldb.com/vuln/391308
vuldb.comvuldb.com/vuln/391308/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes, the affected web functionality is described as remotely reachable. The practical scope depends on network exposure, authentication, and authorization controls.

The available description does not establish whether authentication is required. Access to the endpoint and the ability to submit the affected parameter are the relevant conditions.

Use parameterized queries or prepared statements, validate the identifier as the expected data type, and ensure authorization is checked server-side.

Adopt secure data-access libraries, prohibit SQL string concatenation in review policies, use least-privileged database accounts, and test request-to-query data flows during development and security testing.

Find out what's already
exploitable in your codebase.