dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11483

HIGH · 7.3 CVSS v3.1 Published 2026-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A security flaw has been discovered in SourceCodester Class and Exam Timetabling System 1.0. This affects an unknown function of the file /archive4.php. The manipulation of the argument sy results in sql injection. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks.

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 confidence

SQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0 allows remote attackers to inject malicious SQL queries via the 'sy' parameter in /archive4.php. The lack of input sanitization or parameterized queries in the affected file enables attackers to manipulate database queries, potentially leading to unauthorized data access or exfiltration.

MitigationReplace dynamic SQL queries in archive4.php with parameterized queries/prepared statements to sanitize user input, or apply vendor patch if available. Implement input validation on the 'sy' parameter as an additional layer of defense.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the application installation exists
    Locate the SourceCodester Class and Exam Timetabling System installation directory on the web server. Check for typical paths such as /var/www/html/, /www/, or C:\xampp\htdocs\. Identify the installed version by examining version files, README files, or the application's about/admin pages.
    Affected if The application is installed and the version is 1.0 (or an unpatched version)
  2. Confirm archive4.php exists and is accessible
    Locate the archive4.php file within the web application directory structure. This file is typically found in the root directory of the application. Verify it is accessible via HTTP/HTTPS requests.
    Affected if archive4.php is present in the application root and accessible via the web
  3. Inspect the archive4.php source code for SQL query handling
    Open archive4.php in a text editor or via command line. Search for occurrences of the 'sy' parameter ($_GET['sy'], $_REQUEST['sy'], or similar). Examine how this parameter is incorporated into SQL queries - look for direct string concatenation or interpolation without proper escaping or parameterized queries.
    Affected if The 'sy' parameter is used in SQL queries without parameterized queries (prepared statements) or input sanitization
  4. Verify database user privileges
    Check the database configuration file (typically config.php, db.php, or similar in the application root) to determine the database user credentials. Assess whether the database user has excessive privileges that could be exploited if SQL injection occurs.
    Affected if The database user has privileges beyond what the application requires for normal operation

You are affected if SourceCodester Class and Exam Timetabling System v1.0 is installed, archive4.php is accessible, and the 'sy' parameter is handled in the source code using direct string concatenation in SQL queries rather than prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries in archive4.php with parameterized queries/prepared statements to sanitize user input, or apply vendor patch if available. Implement input validation on the 'sy' parameter as an additional layer of defense.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11483 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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