HIGH 7.3

CVE-2026-13526: 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. An attacker can inject malicious SQL commands through the ID parameter in the /edit_class.php file, allowing remote exploitation without authentication. This flaw enables attackers to read, modify, or delete database records. Public exploits are available, increasing the likelihood of active attacks.

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-06-29 / 2026-06-29

NVD description (verbatim)

A flaw has been found in SourceCodester Class and Exam Timetabling System 1.0. Impacted is an unknown function of the file /edit_class.php. This manipulation of the argument ID causes sql injection. The attack may be initiated remotely. The exploit has been published and may be used.

6 reference(s) · View on NVD →

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

Technical summary

CVE-2026-13526 is a SQL injection vulnerability (CWE-89, CWE-74) affecting SourceCodester Class and Exam Timetabling System 1.0. The vulnerability exists in /edit_class.php where the ID argument is not properly sanitized before being used in database queries. This allows an unauthenticated, remote attacker to execute arbitrary SQL commands via the vulnerable parameter. The CVSS 3.1 score of 7.3 (HIGH) reflects the network-exploitable nature, low complexity of exploitation, and confidentiality/integrity/availability impact. The absence of authentication requirements (PR:N) and user interaction (UI:N) makes this a significant risk.

Business impact

Organizations running this timetabling system face immediate risk of data breach, unauthorized modification of class schedules and exam records, and potential denial of service. Educational institutions relying on this system may experience disruption to scheduling operations, compromised student and staff information, and regulatory compliance violations if personal data is exposed. The published exploit code increases the likelihood of opportunistic attacks. Institutions should prioritize addressing this vulnerability to prevent unauthorized access to sensitive educational data.

Affected systems

SourceCodester Class and Exam Timetabling System version 1.0 is confirmed vulnerable. Other versions have not been explicitly identified in available sources; however, administrators should verify their exact version and consult the vendor for a complete product matrix. Affected deployments are those exposed to untrusted networks or accessible from the internet.

Exploitability

Exploitability is high. The vulnerability requires no authentication, no user interaction, and can be triggered remotely over the network. Attack complexity is low—standard SQL injection techniques apply. The fact that functional exploit code has been published significantly increases practical exploit likelihood. Any system running the vulnerable version and accepting HTTP requests to /edit_class.php is at immediate risk.

Remediation

Immediately upgrade SourceCodester Class and Exam Timetabling System to a patched version released by the vendor. If an immediate patch is unavailable, implement network-level access controls to restrict requests to /edit_class.php to trusted hosts only. Apply input validation and parameterized query frameworks if patching is delayed. Audit database logs for signs of SQL injection attempts and verify the integrity of student records, class assignments, and exam schedules.

Patch guidance

Consult the SourceCodester vendor advisory to identify the patched version addressing CVE-2026-13526. Apply patches in a controlled test environment first to verify compatibility with existing data and integrations. Since this system manages educational records, coordinate patching with institutional scheduling and communication teams to minimize disruption. Verify patching by re-testing the /edit_class.php parameter handling for SQL injection after deployment.

Detection guidance

Monitor web application firewall (WAF) logs for suspicious SQL keywords (UNION, SELECT, DROP, etc.) in HTTP requests to /edit_class.php, particularly in the ID parameter. Review database access logs for unusual query patterns or failed authentication attempts originating from the application. Implement SQL injection detection rules in your WAF or intrusion detection system. Examine application error messages for SQL syntax errors in user-facing responses, which may indicate active exploitation attempts.

Why prioritize this

This vulnerability warrants immediate remediation. It combines high CVSS severity (7.3), network-exploitable attack surface, zero authentication barriers, published exploit availability, and direct access to sensitive educational data. The combination of low barrier to exploitation and significant business impact—particularly in educational environments handling student records—justifies prioritizing this above many other vulnerabilities.

Risk score, explained

The CVSS 3.1 score of 7.3 (HIGH) reflects a vulnerability with network accessibility (AV:N), low attack complexity (AC:L), no privilege requirements (PR:N), and no user interaction needed (UI:N). The impact assessment includes partial loss of confidentiality, integrity, and availability (C:L/I:L/A:L), as an attacker can read sensitive data, modify records, or trigger database errors causing service disruption. The absence of scope change (S:U) indicates the impact is limited to the vulnerable component. Published exploits and the educational nature of affected systems elevate practical risk beyond the base score.

Frequently asked questions

Are there known active attacks exploiting this vulnerability?

While CVE-2026-13526 has not been formally added to CISA's Known Exploited Vulnerabilities (KEV) catalog, functional exploit code is publicly available. This substantially increases the likelihood of opportunistic attack activity. Monitor your systems closely and prioritize patching accordingly.

Can this vulnerability be exploited without modifying the database first?

Yes. The vulnerability allows direct SQL injection through a single HTTP request parameter without requiring prior authentication or database access. An attacker can craft a malicious request immediately upon network access to the application.

What data is most at risk?

The vulnerability affects the entire database underlying the timetabling system, but the most sensitive exposure is likely student records, class assignments, instructor information, and exam schedules. Depending on system configuration, other linked educational data may also be compromised.

If we cannot patch immediately, what interim controls are most effective?

Restrict network access to /edit_class.php using a firewall or WAF to only trusted internal IP ranges. Implement parameterized query frameworks if the application code allows modification. Monitor database logs aggressively for injection signatures. These controls reduce but do not eliminate risk—patching remains essential.

This analysis is based on publicly available information as of June 29, 2026. Vendor advisory details, specific patched versions, and affected product variants should be verified directly with SourceCodester. Organizations should conduct internal testing in non-production environments before applying patches. The absence of KEV catalog status does not indicate low risk—organizations should not delay remediation based on KEV listing alone. No exploit code, proof-of-concept demonstrations, or weaponized tools are provided herein. Source: NVD (public-domain), retrieved 2026-08-07. Analysis generated by SEC.co (claude-haiku-4-5).