CVE-2026-13487: 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 exploit a parameter in the /archive.php file to execute arbitrary SQL commands against the application's database. The vulnerability requires no authentication and can be triggered over the network, making it accessible to remote attackers. Exploit code is already publicly 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-06-28 / 2026-06-29
NVD description (verbatim)
A vulnerability was identified in SourceCodester Class and Exam Timetabling System 1.0. Affected is an unknown function of the file /archive.php. The manipulation of the argument sy leads to sql injection. The attack may be initiated 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
The vulnerability is a SQL injection flaw (CWE-89) in the /archive.php endpoint, where the 'sy' parameter is not properly sanitized before being used in SQL queries. This falls under improper neutralization of special elements used in SQL commands (CWE-74). The attack vector is network-based with no authentication requirements, low attack complexity, and no user interaction needed. The compromised functionality remains within the system's integrity boundary, but allows unauthorized read, write, and delete operations against the database.
Business impact
Successful exploitation allows attackers to read sensitive data from the database, including student records, exam schedules, and administrative information. Attackers can also modify or delete records, disrupting educational operations and compromising data integrity. If the database contains personally identifiable information (PII) of students or staff, a breach could trigger regulatory compliance violations and reputational damage. Availability may also be affected if attackers delete critical scheduling data.
Affected systems
SourceCodester Class and Exam Timetabling System version 1.0 is vulnerable. Organizations running this specific application version should immediately inventory their deployments. The vulnerability is associated with the /archive.php file accessed via the 'sy' parameter. Version numbers for patched releases should be obtained directly from the vendor.
Exploitability
The vulnerability is highly exploitable. It requires no credentials, no user interaction, and can be triggered remotely over standard HTTP requests. The network attack vector combined with low complexity means an attacker with basic SQL injection knowledge can craft a malicious request. The public availability of exploit code significantly raises the likelihood of active exploitation in the wild. Organizations should assume this vulnerability will be actively targeted.
Remediation
Immediately upgrade SourceCodester Class and Exam Timetabling System to a patched version released after June 28, 2026. Verify the specific patch version number through the vendor's official advisory. As an interim measure, implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts targeting /archive.php, particularly those manipulating the 'sy' parameter. Apply database-level access controls to limit what queries can execute and what data they can access.
Patch guidance
Contact SourceCodester or check their official website for available patches. The vendor released updates on or shortly after June 29, 2026. Verify patch version numbers against the official advisory before applying. Test patches in a non-production environment first to ensure compatibility with your configuration. Given the public availability of exploits, patching should be prioritized for immediate deployment.
Detection guidance
Monitor application logs for suspicious SQL syntax in requests to /archive.php, particularly those containing SQL keywords in the 'sy' parameter (e.g., UNION, SELECT, OR 1=1). Implement database activity monitoring to detect unusual query patterns or unauthorized access attempts. Search for HTTP requests with encoded SQL payloads targeting the /archive.php endpoint. Network intrusion detection systems should flag SQL injection signatures. Review authentication and authorization logs for unauthorized database modifications.
Why prioritize this
This vulnerability merits immediate attention due to its CVSS 3.1 score of 7.3 (HIGH severity), public exploit availability, and lack of authentication requirements. The remote network attack vector combined with no user interaction needed creates a low barrier to exploitation. SQL injection vulnerabilities directly enable data theft and system compromise. Educational institutions are frequent targets, and student data theft carries legal and reputational consequences.
Risk score, explained
The CVSS 3.1 score of 7.3 reflects a HIGH severity vulnerability due to the network attack vector (AV:N), low attack complexity (AC:L), no privilege requirements (PR:N), and no user interaction (UI:N). The vulnerability impacts confidentiality, integrity, and availability equally, indicating broad database compromise potential. The published exploit code and educational sector targeting increase real-world risk beyond the base CVSS score.
Frequently asked questions
Who should prioritize this vulnerability?
All organizations running SourceCodester Class and Exam Timetabling System version 1.0 should treat this as critical. Educational institutions should prioritize immediately given the PII exposure risk. Any internet-facing instance is at high risk of compromise.
Can this be exploited without internet access to my system?
No. The vulnerability requires network access to the /archive.php endpoint. If your system is not exposed to the internet or untrusted networks, your risk is lower. However, you should still patch promptly given the ease of exploitation.
What does 'publicly available exploit' mean for my organization?
It means automated tools and detailed attack instructions already exist online. An attacker does not need specialized skills to exploit this. You should assume active scanning and exploitation attempts are occurring against exposed instances.
Is there a temporary fix while waiting for a patch?
Implement WAF rules blocking requests to /archive.php with SQL injection signatures in the 'sy' parameter. Restrict network access to /archive.php to known administrative IPs only. These measures provide partial protection but are not a substitute for patching.
This analysis is based on available vulnerability data as of June 29, 2026. Patch version numbers and detailed vendor guidance should be verified against official SourceCodester advisories. This assessment assumes standard configurations; custom implementations may have different risk profiles. No exploit code is provided or endorsed by SEC.co. Organizations should conduct their own risk assessment and testing before applying any patches or mitigations. Source: NVD (public-domain), retrieved 2026-08-07. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10110HIGHSQL Injection in code-projects Student Details Management System 1.0
- CVE-2026-10111HIGHSQL Injection in sambitraj STUDENT-MANAGEMENT-SYSTEM 1.0 Login
- CVE-2026-10178HIGHSQL Injection in code-projects Online Music Site 1.0 Admin Panel
- CVE-2026-10184HIGHSQL Injection in SourceCodester Hospitals Patient Records System 1.0
- CVE-2026-10185HIGHSQL Injection in SourceCodester Hospitals Patient Records Management System 1.0
- CVE-2026-10186HIGHSQL Injection in Online Hospital Management System 1.0 – Remote Code Execution Risk
- CVE-2026-10208HIGHSQL Injection in Online Hospital Management System Login
- CVE-2026-10225HIGHSQL Injection in PHP Student Management System Login