CVE-2026-15597
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 flaw has been discovered in SourceCodester Class and Exam Timetabling System 1.0/2.php. This affects an unknown function of the file /edit_exam2.php. Performing a manipulation of the argument ID results in sql injection. The attack can be initiated 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 · high confidenceSQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0's edit_exam2.php file allows remote attackers to manipulate the ID parameter to inject arbitrary SQL queries. The vulnerability is remotely exploitable and public exploits are available.
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 is SourceCodester Class and Exam Timetabling SystemInspect the application banner, footer, or source code for the product name. Check the web root directory for the typical file structure of this PHP application.Affected if The installed application is SourceCodester Class and Exam Timetabling System
-
Verify the version is 1.0Look for a version identifier in the application source files, such as in a config file, readme, or the main index page. Compare against the affected version range.Affected if The version is 1.0 or falls within any unpatched version range of this system
-
Locate edit_exam2.php in the web directorySearch the web root for the file edit_exam2.php. Common paths include the admin folder or the root directory of the application.Affected if The file edit_exam2.php exists and is web-accessible
-
Inspect the ID parameter handling in edit_exam2.phpOpen edit_exam2.php and examine how the ID parameter is handled. Look for direct insertion of $_GET['id'] or $_POST['id'] into SQL queries without using prepared statements, parameter binding, or input sanitization.Affected if The ID parameter is used directly in SQL queries without parameterized queries or input validation
-
Confirm database connectivity is enabledVerify the application has a functional database connection by checking the configuration file for database credentials and connection status.Affected if The application connects to a MySQL or other SQL database that can be targeted by the injected queries
The system is affected if it runs SourceCodester Class and Exam Timetabling System version 1.0, has the edit_exam2.php file accessible, and that file uses the ID parameter directly in SQL queries without 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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) in edit_exam2.php, validating and sanitizing all user input before using it in database operations.
- 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-15597 — 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-15597 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