CVE-2026-13486
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/6.php. This impacts an unknown function of the file /preview6.php. Executing a manipulation of the argument course_year_section 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 code via the course_year_section parameter in the preview6.php file. The vulnerable component fails to properly sanitize user input before using it in database queries, enabling attackers to manipulate SQL statements.
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.
-
Locate the application installationSearch for preview6.php file in the web server's document root or application directory. Common paths may include /preview6.php or /pages/preview6.php.Affected if preview6.php file exists in the application directory tree.
-
Verify the application versionCheck for version indicators such as a version.php file, footer, or readme.txt in the application root. Compare against the affected version 1.0.Affected if The installed version is Class and Exam Timetabling System 1.0.
-
Inspect the vulnerable code in preview6.phpOpen preview6.php and search for occurrences of 'course_year_section' variable. Check if this parameter is directly inserted into SQL queries without using prepared statements, parameterized queries, or proper sanitization functions like mysqli_real_escape_string or PDO::quote.Affected if The course_year_section parameter is used in SQL queries without parameterized binding or input escaping.
-
Test for SQL injection vulnerabilityIf the application is live or testable, send a request to preview6.php with the course_year_section parameter set to a SQL injection test payload such as ' OR '1'='1. Observe if unexpected database data is returned or if the query behaves differently than expected.Affected if The application returns different results when injecting SQL syntax, indicating the parameter is not properly sanitized.
You are affected if SourceCodester Class and Exam Timetabling System version 1.0 is installed and preview6.php exists with the course_year_section parameter being used in unsanitized SQL queries.
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 or parameterized queries with bound parameters to safely handle user input in database operations. Additionally, apply input validation and escaping for the course_year_section parameter, and conduct a comprehensive security review of all PHP files in the application for similar injection flaws.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13486 — 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-13486 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