CVE-2026-11482
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 identified in SourceCodester Class and Exam Timetabling System 1.0. The impacted element is an unknown function of the file /archive5.php. The manipulation of the argument sy leads to sql injection. The attack can be initiated remotely. The exploit is publicly available and might 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 in the /archive5.php file via the 'sy' parameter allows remote attackers to inject arbitrary 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 identityIdentify if the deployed application is SourceCodester Class and Exam Timetabling System version 1.0 by checking application files, headers, or documentationAffected if The application is SourceCodester Class and Exam Timetabling System version 1.0
-
Locate vulnerable scriptSearch for the presence of archive5.php in the web root or application directoryAffected if archive5.php exists in the application
-
Inspect SQL query handlingExamine the source code of archive5.php and look for how the 'sy' parameter is handled in SQL queries - check if user input is directly concatenated into SQL statements without parameterized queries or input sanitizationAffected if The 'sy' parameter is used directly in SQL queries without prepared statements, sanitization, or parameter binding
-
Verify database layerReview database connection and query execution code to determine if PDO prepared statements or mysqli prepared statements are being used for queries involving the 'sy' parameterAffected if Parameterized queries are not used for the 'sy' parameter in archive5.php
-
Test parameter injectionIf you have authorization, send a crafted request to archive5.php with the 'sy' parameter containing SQL meta-characters (such as a single quote) and observe if SQL errors are returned or behavior changesAffected if The application returns SQL errors or exhibits unexpected behavior when special SQL characters are passed in the 'sy' parameter
You are affected if you are running SourceCodester Class and Exam Timetabling System 1.0 and the archive5.php file contains direct string concatenation of the 'sy' parameter into SQL queries without using parameterized 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 dataReplace dynamic SQL queries with parameterized queries or prepared statements; validate and sanitize all user inputs before using them in database queries.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11482 — 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-11482 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