CVE-2026-14733
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 detected in SourceCodester Class and Exam Timetabling System 1.0. This issue affects some unknown processing of the file /edit_coursea.php. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit is now public and may be used.
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_coursea.php file allows remote attackers to inject malicious SQL queries via the unsanitized ID parameter.
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 SourceCodester Class and Exam Timetabling System installationCheck your web server document root for the presence of the application files, particularly look for the edit_coursea.php file in the application directoryAffected if The application is installed and edit_coursea.php exists in the web-accessible directory
-
Verify application version is 1.0Check for a version file, README, or any version indicator within the application directory; if no version file exists, check the file metadata or any installer files that may indicate the installed versionAffected if The installed version is 1.0 or cannot be determined but the file structure matches the reported vulnerable version
-
Examine edit_coursea.php for SQL query handlingOpen edit_coursea.php in a text editor and locate the code that handles the ID parameter; search for SQL queries (SELECT, INSERT, UPDATE, DELETE) that incorporate the ID parameter directly without using prepared statements or parameter bindingAffected if The ID parameter from GET or POST request is used directly in SQL queries without sanitization or parameter binding
-
Check if application has a database connectionVerify the application connects to a MySQL or MariaDB database by checking configuration files for database credentials and connection stringsAffected if The application uses a database and edit_coursea.php executes SQL queries against it using the unsanitized ID parameter
-
Test ID parameter for SQL injection susceptibilityIf you have authorized access, send a crafted request to edit_coursea.php with SQL metacharacters in the ID parameter (e.g., ID=1' OR '1'='1) and observe whether the application returns database errors or unexpected behaviorAffected if The application returns SQL syntax errors or behaves differently based on SQL injection payloads in the ID parameter
You are affected if you have SourceCodester Class and Exam Timetabling System version 1.0 installed with edit_coursea.php containing direct SQL query construction using the unsanitized ID parameter from user input.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements in edit_coursea.php and validate/sanitize all user inputs before database operations.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14733 — 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-14733 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