CVE-2026-11486
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. Affected by this vulnerability is an unknown functionality of the file /archive1.php. Performing a manipulation of the argument sy results in sql injection. Remote exploitation of the attack is possible. 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 · high confidenceSQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0's /archive1.php file. The 'sy' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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 vulnerable file archive1.phpSearch web server document roots for archive1.php. On Linux: 'find /var/www -name archive1.php 2>/dev/null' or 'find /home -name archive1.php 2>/dev/null'. On Windows IIS/Apache: check typical web directories like C:\inetpub\wwwroot or where you installed the application.Affected if The file archive1.php exists in any web-accessible directory.
-
Confirm application versionCheck for version files (version.txt, README, or version in footer/meta tags of index.php). Search source code for version strings like '1.0' or 'version'. If no version file exists, check the application's main page or about page.Affected if The installed version is 1.0 or the version cannot be determined (treat unknown versions as potentially affected).
-
Verify the vulnerable parameter exists in the codeOpen archive1.php and search for usage of the 'sy' parameter. Look for code patterns like $_GET['sy'], $_POST['sy'], or Request::input('sy') that handle this parameter. Identify if it is used in database queries.Affected if The 'sy' parameter is being read and used in database queries within archive1.php.
-
Check if the SQL query lacks parameterized preparationIn archive1.php, examine the SQL query that uses the 'sy' parameter. Look for whether the query uses prepared statements (prepare, bindParam, bindValue), PDO with parameter binding, or mysqli with placeholders. Check if the parameter is concatenated or interpolated directly into the SQL string.Affected if The 'sy' parameter is directly concatenated into the SQL query string without using prepared statements or proper escaping functions.
You are affected if archive1.php exists in your SourceCodester Class and Exam Timetabling System installation, the application version is 1.0 or unknown, and the 'sy' parameter is used in SQL queries without prepared statement protection.
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 query construction with parameterized queries/prepared statements. Implement proper input validation and sanitization for all user-supplied parameters before database interaction.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11486 — 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-11486 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