dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14732

HIGH · 7.3 CVSS v3.1 Published 2026-07-05
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 7 weeks old

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 vulnerability has been detected in SourceCodester Class and Exam Timetabling System 1.0. This vulnerability affects unknown code of the file /edit_exam.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated 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 · moderate confidence

SQL injection vulnerability in SourceCodester Class and Exam Timetabling System 1.0 where the ID parameter in /edit_exam.php is not properly sanitized, allowing attackers to inject malicious SQL queries through the argument.

MitigationImplement prepared statements/parameterized queries for all database operations involving user input. Apply input validation and sanitize the ID parameter before using it in SQL queries.

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. Identify the installed application
    Check if the web application 'SourceCodester Class and Exam Timetabling System' is present on the server by searching for its installation directories or files (common paths include /var/www/html/, /www/, or the application's specific folder). Look for application files or check web server configuration for this application name.
    Affected if The application is not installed on the system.
  2. Verify the application version
    Locate a version file, README, or any file containing version information within the application's root directory. Compare the found version to '1.0'. If no version is explicitly stated, check file timestamps or modification dates as indicators of the installation version.
    Affected if The installed version is NOT 1.0.
  3. Confirm the vulnerable file exists
    Locate the file 'edit_exam.php' within the application's web-accessible directory structure (typically in the main application folder or an 'admin' or 'exam' subdirectory). Verify the file exists on the filesystem.
    Affected if The file edit_exam.php does not exist in the application directory.
  4. Check network exposure of the vulnerable endpoint
    Determine if the edit_exam.php file is accessible over the network by accessing the URL (for example: http://[hostname]/edit_exam.php or similar path). Verify the application is responding to HTTP requests.
    Affected if The application is not accessible over the network or edit_exam.php is not reachable.
  5. Inspect the ID parameter handling in edit_exam.php
    Examine the source code of edit_exam.php for how the 'ID' parameter is handled. Look for SQL queries that directly use the ID parameter without prepared statements, parameter binding, or input sanitization functions.
    Affected if The ID parameter is processed using prepared statements or proper sanitization functions.

A system is affected if it runs SourceCodester Class and Exam Timetabling System version 1.0, has the edit_exam.php file accessible, and the ID parameter in that file is used in SQL queries without sanitization or 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

Implement prepared statements/parameterized queries for all database operations involving user input. Apply input validation and sanitize the ID parameter before using it in SQL queries.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14732 — 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-14732 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