CVE-2026-13565
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/1.php. Affected by this vulnerability is an unknown functionality of the file /edit_class1.php. Executing a manipulation of the argument ID can lead to sql injection. The attack can be launched 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 allows remote attackers to inject malicious SQL queries via the ID parameter in /edit_class1.php. The application fails to properly sanitize or parameterize user input before using it in SQL queries.
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.
-
Verify the application is installedLocate SourceCodester Class and Exam Timetabling System files in the web root directory (commonly /var/www/html, /www, or similar). Look for the application's main directory structure containing edit_class1.php.Affected if The application directory containing edit_class1.php exists on the server.
-
Confirm the application versionCheck for a version indicator in the application - typically in a README file, version.php, or the main index page footer. The affected version is 1.0.Affected if The installed version matches 1.0.
-
Locate the vulnerable fileVerify that edit_class1.php exists in the web-accessible directory. Common paths include /edit_class1.php or /path/to/application/edit_class1.php.Affected if The file edit_class1.php exists in the web root or application directory.
-
Inspect the ID parameter handling in edit_class1.phpOpen edit_class1.php and examine how the 'ID' parameter is handled. Look for direct use of $_GET['ID'] or $_POST['ID'] in SQL queries without prepared statements, parameterization, or input sanitization functions like mysqli_real_escape_string or PDO::prepare.Affected if The ID parameter is used directly in SQL queries without parameterized binding or escaping functions.
-
Test the parameter externally (if authorized)With explicit authorization, send a crafted request such as edit_class1.php?ID=1' OR '1'='1 to observe if the application returns SQL error messages or behaves differently than expected.Affected if The application returns SQL syntax errors or unexpected results indicating unsanitized input is being processed.
If SourceCodester Class and Exam Timetabling System version 1.0 is installed with edit_class1.php present and the ID parameter is handled without prepared statements or input sanitization, the environment is affected by CVE-2026-13565.
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 prepared statements/parameterized queries for all database operations in edit_class1.php, particularly for the ID parameter. Additionally, implement input validation and employ least-privilege database accounts to limit the impact of any successful SQL injection.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13565 — 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-13565 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