CVE-2026-14641
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was determined in SourceCodester Class and Exam Timetabling System 1.0. Affected by this vulnerability is an unknown functionality of the file /edit_course.php. Executing a manipulation of the argument ID can lead to sql injection. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0's /edit_course.php file. The ID parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code and potentially exfiltrate, modify, or delete database contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the application is SourceCodester Class and Exam Timetabling SystemInspect the application source code for version identifiers - check for version strings in header comments, README files, or an about/admin page. Compare the installed version to 1.0.Affected if The installed version is Class and Exam Timetabling System 1.0
-
Locate the edit_course.php fileSearch the web root directory for the file edit_course.php. Common paths may include /admin/edit_course.php, /pages/edit_course.php, or /edit_course.php directly in the web root.Affected if The file edit_course.php exists in the web application directory
-
Inspect the ID parameter handling in edit_course.phpOpen edit_course.php and examine how the ID parameter is retrieved (e.g., $_GET['id'], $_POST['id'], $_REQUEST['id']). Check if this value is directly concatenated into SQL queries without using prepared statements, parameterized queries, or proper sanitization functions.Affected if The ID parameter is used directly in SQL queries without prepared statements or input sanitization
-
Verify database connectivityCheck if the application is configured with a functional database connection (MySQL/MariaDB). SQL injection requires an active database connection to be exploitable.Affected if The application connects to a MySQL/MariaDB database and the vulnerable edit_course.php is accessible via HTTP
You are affected if you are running SourceCodester Class and Exam Timetabling System version 1.0, the edit_course.php file exists in your environment, and the ID parameter in that file is used directly in SQL queries without prepared statements or sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries (prepared statements) for all database operations in edit_course.php, particularly for the ID parameter. Additionally, apply input validation and output encoding as defense-in-depth measures.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data