HIGH 7.3

CVE-2026-14772: 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 affecting the /edit_course1.php file. An attacker can manipulate the ID parameter to inject arbitrary SQL commands, potentially reading, modifying, or deleting database records. The vulnerability requires no authentication and can be exploited over the network. Public disclosure has occurred, increasing exploitation risk.

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-05 / 2026-07-06

NVD description (verbatim)

A vulnerability has been found in SourceCodester Class and Exam Timetabling System 1.0/1.php. The impacted element is an unknown function of the file /edit_course1.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

6 reference(s) · View on NVD →

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

Technical summary

The vulnerability is a classic SQL injection flaw (CWE-89) in the /edit_course1.php endpoint of SourceCodester Class and Exam Timetabling System 1.0. The ID parameter is passed unsafely to database queries without proper input validation or parameterized statement use. The affected function name is listed as unknown in vendor records, suggesting the codebase may lack clear documentation. The flaw also falls under CWE-74 (Improper Neutralization of Special Elements), indicating insufficient sanitization of user-controlled input before SQL execution. No authentication is required to trigger the vulnerability.

Business impact

Successful exploitation could allow an attacker to access, modify, or destroy course and exam timetable records in the database. For educational institutions using this system, this could result in course schedule corruption, unauthorized grade or enrollment modifications, student data theft, and operational disruption during critical scheduling periods. The impact extends to confidentiality, integrity, and availability of educational data. Reputational damage and potential regulatory exposure (FERPA, GDPR, local privacy laws) are secondary concerns depending on jurisdiction and student data classification.

Affected systems

SourceCodester Class and Exam Timetabling System version 1.0 is affected. The vulnerability is present in the /edit_course1.php file. Organizations running this exact version in production should assume exposure. The vendor product list is not populated in official sources, suggesting this may be an open-source or lesser-tracked solution; verify your deployment version against vendor advisory documentation.

Exploitability

This vulnerability scores 7.3 HIGH on CVSS v3.1 due to its network-accessible nature (AV:N), lack of authentication requirement (PR:N), low complexity (AC:L), and impact to confidentiality, integrity, and availability. Exploitation requires basic knowledge of SQL injection techniques and HTTP request manipulation—tools and payloads are readily available. Public disclosure increases the risk of automated scanning and weaponized exploitation. The vulnerability is not yet tracked in the CISA Known Exploited Vulnerabilities catalog, but public availability of exploit details removes a barrier to adoption by threat actors.

Remediation

Immediately apply vendor patches or upgrade to a version released after this disclosure. If patches are unavailable, implement input validation on the ID parameter (whitelist numeric or expected formats), use parameterized queries or prepared statements for all database interactions, and enforce principle of least privilege on database accounts. Deploy a Web Application Firewall (WAF) rule to block SQL injection payloads as a temporary layer. Conduct a database audit to detect unauthorized modifications or data exfiltration post-disclosure.

Patch guidance

Contact SourceCodester or check their official advisory portal for patched versions of Class and Exam Timetabling System. Verify patch applicability to version 1.0 specifically. If automatic updates are available, prioritize this patch in your maintenance window. Test patches in a non-production environment before production rollout to ensure compatibility with local customizations or data. If vendor support is unavailable or slow, consider evaluating alternative scheduling solutions.

Detection guidance

Monitor /edit_course1.php access logs for unusual ID parameter values, especially those containing SQL metacharacters (single quotes, dashes, semicolons, keywords like UNION, SELECT, DROP). Set up alerts for HTTP 400/500 errors on this endpoint, which may indicate injection attempt failures. Use database query logging to detect suspicious SQL patterns or unexpected table access from the application user account. SIEM rules should flag multiple rapid requests to /edit_course1.php with varying payloads, typical of automated exploitation scanning.

Why prioritize this

This vulnerability merits immediate attention because it is network-exploitable without authentication, has been publicly disclosed, impacts data confidentiality and integrity, and affects an educational timetabling system likely managing sensitive student and course data. The HIGH CVSS score reflects the combination of easy access and broad impact. Organizations using version 1.0 should treat this as critical until patched.

Risk score, explained

CVSS 7.3 reflects a high-risk vulnerability: remote network access (AV:N) with no authentication barrier (PR:N) makes it trivial to reach. Low attack complexity (AC:L) means attackers need no special conditions or timing. The impact to confidentiality, integrity, and availability (C:L, I:L, A:L) means an attacker can read database records, modify timetables or grades, and potentially delete data, affecting all three security pillars. The score would be 9.8 CRITICAL if system-level impact (S:C) were present, but isolation to the application scope keeps it at HIGH.

Frequently asked questions

We use SourceCodester Class and Exam Timetabling System but are unsure of our version. How do we check?

Log into the application and check the footer, about page, or admin settings for version information. Review your deployment files or installation documentation. If the version is 1.0, apply the patch immediately. Contact your administrator or the vendor if version information is unclear.

Do we need to wipe our database after this vulnerability was disclosed?

Not necessarily, but a forensic audit is recommended. Query your database logs (if available) for suspicious activity or modifications coinciding with the disclosure date and your discovery. Look for unexpected changes to course records, grades, or user accounts. If you find evidence of unauthorized access, restore from a clean backup and investigate further.

Is there a temporary fix if we cannot patch immediately?

A WAF rule blocking SQL injection patterns on the /edit_course1.php ID parameter can reduce exposure while you prepare a patch. However, WAF rules are not a substitute for patching and may generate false positives. Enforce strict network access controls (restrict access to this application to trusted IP ranges if possible) and implement database account privilege minimization. Patch as soon as feasible.

How does this compare in severity to other educational software vulnerabilities?

SQL injection in unauthenticated contexts consistently ranks as high-severity because it bypasses application logic and accesses data directly. Educational systems handling FERPA-protected data are especially critical. This vulnerability is on par with other remote SQL injection flaws in web applications, and should be prioritized ahead of lower-impact issues like cross-site scripting.

This analysis is provided for informational purposes to help organizations assess and prioritize vulnerability remediation. It is not a substitute for vendor advisories, security assessments, or legal counsel. We do not provide exploit code or step-by-step weaponization guidance. Readers are responsible for verifying patch versions, testing in their environment, and complying with all applicable software licenses and regulations. Patch availability and vendor support status should be confirmed directly with SourceCodester before remediation planning. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).