CVE-2026-13487
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. Affected is an unknown function of the file /archive.php. The manipulation of the argument sy leads to sql injection. The attack may 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 · high confidenceA SQL injection vulnerability exists in SourceCodester Class and Exam Timetabling System 1.0 within the /archive.php file. The 'sy' parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries via the argument sy.
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 the application installationLocate and identify SourceCodester Class and Exam Timetabling System 1.0 by checking for the main application files or directory structure typically deployed with this systemAffected if The system is running SourceCodester Class and Exam Timetabling System version 1.0
-
Locate the vulnerable archive.php fileSearch the web root or application directory for the file archive.phpAffected if The archive.php file exists in the deployed application
-
Verify the sy parameter is handled by archive.phpExamine archive.php source code and look for code that processes the 'sy' parameter from GET or POST requests, typically using $_REQUEST['sy'], $_GET['sy'], or $_POST['sy']Affected if The archive.php file processes a 'sy' parameter without visible sanitization or prepared statements
-
Confirm database interaction with sy parameterSearch the archive.php code for database query execution (such as mysqli_query, mysql_query, PDO query, or similar) where the 'sy' parameter value is directly concatenated or interpolated into the SQL stringAffected if The 'sy' parameter is used directly in SQL queries without parameterized binding
-
Test if the sy parameter is accessibleAttempt to access archive.php with a test value for the sy parameter via HTTP request to verify the parameter is accepted and processedAffected if The sy parameter is accepted and processed by the archive.php endpoint
A user is affected if they run SourceCodester Class and Exam Timetabling System version 1.0 with the archive.php file present and the 'sy' parameter being processed in SQL queries without proper sanitization or prepared statements.
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/parameterized queries for database operations involving the 'sy' parameter in archive.php, and add input validation to ensure only expected data types are accepted.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13487 — 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-13487 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