CVE-2026-11485
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 security vulnerability has been detected in SourceCodester Class and Exam Timetabling System 1.0. Affected is an unknown function of the file /archive2.php. Such manipulation of the argument sy leads to sql injection. The attack may be launched remotely. The exploit has been disclosed publicly 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 archive2.php file. The 'sy' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.
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 application identity and versionLocate the application's version information - typically found in an about page, footer, or readme file included with the installation.Affected if The application is SourceCodester Class and Exam Timetabling System version 1.0
-
Locate the vulnerable PHP fileCheck if the file /archive2.php exists in the web root or application directory.Affected if The file archive2.php is present in the application installation
-
Inspect the SQL query implementation for the sy parameterOpen archive2.php and locate the code handling the 'sy' parameter. Search for the SQL query where this parameter is used.Affected if The 'sy' parameter is directly concatenated into a SQL query string without using prepared statements or parameter binding
-
Verify input sanitization is absentExamine the code around the 'sy' parameter usage to check if any sanitization functions (such as mysqli_real_escape_string, htmlspecialchars for SQL contexts, or input validation) are applied before the SQL query execution.Affected if No input validation or escaping functions are applied to the 'sy' parameter before it is used in the SQL query
-
Test the parameter for injection (authorized testing only)If you have authorization, send a crafted request to /archive2.php with the 'sy' parameter containing SQL injection syntax (e.g., sy=1' OR '1'='1) and observe the application's response.Affected if The application returns database errors or exhibits unexpected behavior indicating SQL injection is possible
The environment is affected if it runs SourceCodester Class and Exam Timetabling System version 1.0 and the archive2.php file directly uses the 'sy' parameter in SQL queries without prepared statements or input 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 dataReplace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation on the 'sy' parameter. If immediate patching is not possible, implement WAF rules as a temporary mitigation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11485 — 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-11485 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