HIGH 7.3

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

A SQL injection vulnerability has been identified in SourceCodester Class and Exam Timetabling System version 1.0. The flaw exists in the /edit_product.php file where user-supplied input in the ID parameter is not properly validated before being used in database queries. An attacker can exploit this remotely without authentication to execute arbitrary SQL commands, potentially reading, modifying, or deleting sensitive data. Public exploit code is available, elevating the practical 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 flaw has been found in SourceCodester Class and Exam Timetabling System 1.0. Impacted is an unknown function of the file /edit_product.php. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. 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

The vulnerability is a classic SQL injection flaw (CWE-89) combined with improper input neutralization (CWE-74) in the /edit_product.php endpoint. The ID argument passes unsanitized user input directly into SQL queries, allowing attackers to inject arbitrary SQL syntax. The CVSS 3.1 score of 7.3 (HIGH) reflects network-accessible exploitation with no authentication or user interaction required, yielding confidentiality, integrity, and availability impact. The availability of published exploits significantly increases real-world risk.

Business impact

Organizations deploying SourceCodester Class and Exam Timetabling System 1.0 face exposure of student records, exam schedules, and instructor data. Attackers can extract credentials, modify grades or timetables, or disable the application entirely. For educational institutions relying on this system for operations, such compromise disrupts scheduling, compromises data privacy (potentially triggering regulatory violations), and damages reputation. The low barrier to exploitation—no authentication required—means threat actors can act opportunistically.

Affected systems

SourceCodester Class and Exam Timetabling System version 1.0 is affected. The vulnerability resides specifically in /edit_product.php. Any instance accessible over a network is vulnerable. Verify your deployment version and confirm whether this legacy application is still in active use in your environment, as it may have been replaced by patched or redesigned alternatives.

Exploitability

Exploitability is straightforward and practical. The attack requires only network access and basic SQL injection knowledge; no valid credentials, special privileges, or user interaction are needed. Published exploit code lowers the skill floor, meaning script-based attacks are likely. CVSS vector AV:N/AC:L/PR:N/UI:N reflects this ease. Organizations should assume active reconnaissance and exploitation attempts are already occurring.

Remediation

Immediate action is required. Check whether your organization is running SourceCodester Class and Exam Timetabling System 1.0. If so, contact the vendor urgently to determine availability of patched versions or security updates. If no patch exists, isolate the application from untrusted networks, restrict access by IP allowlist, and consider disabling the /edit_product.php endpoint if functionality allows. As a longer-term measure, consider migrating to a modern, actively maintained timetabling solution with security-first design.

Patch guidance

Verify directly with SourceCodester for patched release availability and specific version numbers. Given the publication date of July 2026, check the vendor's security advisories and release notes for any 1.0.1 or higher versions explicitly addressing this SQL injection. Apply patches in a controlled test environment first to ensure compatibility with your exam schedules and data workflows before production deployment.

Detection guidance

Monitor /edit_product.php for suspicious HTTP requests containing SQL keywords (SELECT, UNION, OR, --, ;) in the ID parameter or other query strings. Log and alert on database errors or unexpected query patterns. Implement Web Application Firewall (WAF) rules to block common SQL injection payloads. Search historical logs for patterns matching published exploit signatures to identify potential prior breaches. Database query logging will reveal injected SQL if the application is already compromised.

Why prioritize this

This vulnerability warrants immediate prioritization due to the convergence of high CVSS severity (7.3), unauthenticated remote exploitability, published exploit availability, and the sensitive nature of educational data at risk. The lack of complexity and immediate practical threat make delay costly. While not yet listed in CISA's KEV catalog, the publication of working exploits means active weaponization is probable.

Risk score, explained

The CVSS 3.1 score of 7.3 (HIGH) accurately reflects a network-accessible SQL injection with no authentication barrier and confidentiality, integrity, and availability impacts. The presence of published exploits and the absence of KEV listing (as of the modification date) suggest awareness in attacker communities. For educational institutions or any organization using this system, the effective risk is higher due to data sensitivity and operational criticality; treat as critical priority regardless of the baseline score.

Frequently asked questions

Is this vulnerability being actively exploited?

The vulnerability has a published exploit and no CISA KEV tracking as of this writing. While we cannot confirm active in-the-wild exploitation definitively, the availability of working code means attackers have low barriers to weaponization. Assume exploitation is possible immediately and prioritize accordingly.

Do I need to take action if I don't use SourceCodester Class and Exam Timetabling System?

No. This vulnerability is specific to SourceCodester's timetabling application version 1.0. If your institution uses other scheduling or exam management tools, verify your vendor and version to confirm you are not affected. If uncertain, audit your running services.

What should I do if I discover my system was already compromised via this flaw?

Immediately isolate the affected application from the network, secure database credentials, and initiate incident response. Review database logs and backup audit trails for evidence of unauthorized queries or data exfiltration. Notify affected users (students, staff) as required by applicable data protection regulations. Engage your forensics team to determine scope and timeline of compromise.

Are there workarounds if a patch is not yet available?

Temporary mitigations include network segmentation (restrict access to /edit_product.php by IP), disabling the endpoint if functionality allows, implementing WAF rules blocking SQL injection patterns, and applying database least-privilege access controls. These are not substitutes for patching; they buy time only.

This analysis is provided for informational and defensive purposes only. SEC.co does not confirm active exploitation or provide prediction of future attacks. Patch availability, version numbers, and vendor timelines must be verified directly with SourceCodester and your internal IT operations. This explainer does not constitute official security advisory; refer to the vendor's official guidance for authoritative mitigation steps. Organizations should conduct their own risk assessment based on their specific deployment and data sensitivity. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).