HIGH 7.3

CVE-2026-14642 SQL Injection in SourceCodester Class and Exam Timetabling System 1.0

A SQL injection vulnerability exists in SourceCodester Class and Exam Timetabling System version 1.0 in the /edit_class2.php file. An attacker can manipulate the ID parameter to inject malicious SQL commands, potentially allowing unauthorized access to or modification of the database. The vulnerability requires no authentication and can be exploited remotely. Public exploit code is available, increasing the risk of active exploitation.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-74, CWE-89
Affected products
0 configuration(s)
Published / Modified
2026-07-04 / 2026-07-06

NVD description (verbatim)

A vulnerability was identified in SourceCodester Class and Exam Timetabling System 1.0. Affected by this issue is some unknown functionality of the file /edit_class2.php. The manipulation of the argument ID leads to sql injection. The attack is possible to be carried out remotely. The exploit is publicly available and might be used.

6 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14642 is a remote SQL injection flaw (CWE-89, CWE-74) affecting SourceCodester Class and Exam Timetabling System 1.0. The vulnerability exists in /edit_class2.php where user-supplied input in the ID parameter is not properly sanitized before being incorporated into SQL queries. The CVSS 3.1 score of 7.3 (HIGH) reflects the network-based attack vector, low complexity, and lack of required privileges or user interaction. The vulnerability enables confidentiality, integrity, and availability compromise of the underlying database.

Business impact

Exploitation of this SQL injection could allow attackers to extract sensitive educational data (student records, grades, schedules), modify class assignments or timetables, or delete database records. Organizations using this system for exam scheduling and class management face operational disruption, data breach liability, and potential regulatory exposure if student or staff information is compromised. The availability of public exploit code elevates the likelihood of opportunistic attacks.

Affected systems

SourceCodester Class and Exam Timetabling System version 1.0 is affected. Organizations using this self-hosted or on-premise educational management system are in scope. The vulnerability is not version-specific beyond 1.0; verify whether newer versions have been released and whether your deployment matches the affected version.

Exploitability

This vulnerability is easily exploitable. It requires only network access to the /edit_class2.php endpoint—no authentication, user interaction, or special conditions are needed. Public exploit code is available, meaning attackers have ready-made tools to probe and compromise affected systems. The low complexity and high accessibility make this a priority target for automated scanning and attacks.

Remediation

Immediate action is required. Contact SourceCodester or check their vendor website for a patched version. If no patch is available, consider implementing Web Application Firewall (WAF) rules to filter SQL injection patterns in the ID parameter, restricting network access to /edit_class2.php to trusted networks, or temporarily taking the application offline if it is not critical. Input validation and parameterized queries must be enforced in any code update.

Patch guidance

Verify the latest version of SourceCodester Class and Exam Timetabling System against the vendor's official advisory or download page. Apply updates according to the vendor's release notes. If the vendor has not released a patch, request an estimated timeline and implement compensating controls (network segmentation, WAF rules, access restrictions) while awaiting an update.

Detection guidance

Monitor web server logs and database logs for suspicious SQL queries, unusual characters in URL parameters (such as quotes, semicolons, UNION keywords), and failed SQL statements. Search for requests to /edit_class2.php with encoded or raw SQL syntax in the ID parameter. Configure intrusion detection signatures for SQL injection payloads. Review database access logs for unexpected queries or data extraction patterns.

Why prioritize this

This vulnerability merits urgent remediation due to the convergence of high CVSS score (7.3), public exploit availability, minimal attack complexity, and the lack of authentication barriers. Educational institutions managing sensitive student data face significant operational and compliance risks. The broad impact potential (confidentiality, integrity, availability) and ease of exploitation justify prioritization above many other vulnerabilities.

Risk score, explained

The CVSS 3.1 score of 7.3 reflects a HIGH severity rating. The network attack vector (AV:N) and no privilege requirement (PR:N) indicate broad accessibility. Low attack complexity (AC:L) and no user interaction (UI:N) mean attackers can exploit this reliably and automatically. The scoped-unchanged model (S:U) applies the impact to the vulnerable component's resources. Low impact values for confidentiality, integrity, and availability (each L) account for partial compromise—the attacker can read, modify, or disrupt database records but may not achieve complete system takeover. The convergence of accessibility and impact justifies the HIGH rating.

Frequently asked questions

Is there a publicly available patch for CVE-2026-14642?

Based on the current vulnerability record, no patch information is listed. Organizations should contact SourceCodester directly or monitor their official channels for patch releases. In the interim, implement network controls and WAF rules to mitigate exploitation risk.

Can this vulnerability be exploited without credentials?

Yes. The vulnerability requires no authentication, meaning any attacker with network access to the application can attempt exploitation. This significantly increases the attack surface and urgency.

What is the practical impact of a successful SQL injection here?

An attacker can query, modify, or delete database records. In an educational context, this could mean stealing student grades, altering enrollment records, disrupting exam schedules, or exfiltrating personal information stored in the database.

Should we assume public exploit code is actively being used?

Yes. The availability of public exploits means attackers have low barriers to entry. Assume malicious scanning and exploitation attempts are occurring or will occur shortly if your system is exposed to the internet. Prioritize patching or isolation immediately.

This analysis is based on the CVE record dated July 4–6, 2026. Patch and version information should be verified directly with SourceCodester's official sources. No exploit code, proof-of-concept, or weaponized attack procedures are included here. Organizations are responsible for assessing their exposure, testing patches in non-production environments, and implementing remediations according to their risk tolerance and operational requirements. This content is for informational purposes and does not constitute professional security advice. Source: NVD (public-domain), retrieved 2026-08-13. Analysis generated by SEC.co (claude-haiku-4-5).