PatchSiren cyber security CVE debrief
CVE-2026-14641 SourceCodester CVE debrief
A SQL injection vulnerability was discovered in the SourceCodester Class and Exam Timetabling System 1.0. The issue affects an unknown functionality within the /edit_course.php file. By manipulating the ID argument, an attacker can inject malicious SQL code, enabling remote attacks. The vulnerability has been publicly disclosed and may be exploited. Evidence from Vuldb and NVD confirms the vulnerability's existence and provides details on its CVSS score and severity.
- Vendor
- SourceCodester
- Product
- Class and Exam Timetabling System
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-04
- Original CVE updated
- 2026-07-04
- Advisory published
- 2026-07-04
- Advisory updated
- 2026-07-04
Who should care
System administrators and security teams responsible for SourceCodester Class and Exam Timetabling System 1.0 should prioritize patching this vulnerability. Given its medium CVSS severity score of 5.5, organizations must assess their exposure and take appropriate defensive actions to prevent potential SQL injection attacks.
Technical summary
The CVE-2026-14641 vulnerability is caused by inadequate input validation in the /edit_course.php file of the SourceCodester Class and Exam Timetabling System 1.0. This allows attackers to inject malicious SQL code through the ID argument. The vulnerability has a CVSS score of 5.5, indicating medium severity. It is categorized under CWE-74 and CWE-89, highlighting improper neutralization of special elements in SQL commands.
Defensive priority
Apply patches or updates provided by the vendor to address the SQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0. Conduct thorough inventory checks to identify exposed systems and prioritize remediation efforts based on risk assessment.
Recommended defensive actions
- Apply patches or updates provided by the vendor to address the SQL injection vulnerability.
- Conduct thorough inventory checks to identify exposed systems.
- Prioritize remediation efforts based on risk assessment.
- Implement additional monitoring and logging to detect potential exploitation attempts.
- Consider compensating controls, such as web application firewalls, to mitigate the risk.
Evidence notes
The CVE-2026-14641 vulnerability is confirmed by multiple sources, including Vuldb and NVD. The CVSS score of 5.5 indicates medium severity. However, the lack of detailed information on affected scope and vendor remediation workflow requires defenders to take cautious and proactive measures.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-14641 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-14641
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-14641 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-14641
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/sunjingyuan123/ccvvee/issues/2
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-14641
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/846143
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/847955
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/376157
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/376157/cti
-
Source reference
Unverified legacy reference
URL: https://www.sourcecodester.com/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.