dbcve.org
InjectionWeakness · CWE-74

CVE-2026-14771

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 flaw has been found in SourceCodester Class and Exam Timetabling System 1.0/1.php. The affected element is an unknown function of the file /edit_exam1.php. Executing a manipulation of the argument ID can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published 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's /edit_exam1.php file allows remote attackers to manipulate the ID parameter to inject arbitrary SQL commands into the database query.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the ID parameter, implement strict input validation, and apply least-privilege database access.

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. Confirm installed software version
    Locate the SourceCodester Class and Exam Timetabling System installation and check the version number in the application documentation, header, or about page. Typical install path may be /var/www/html/ or /htdocs/ on web servers.
    Affected if The installed version is 1.0 or matches the affected version range for this system
  2. Locate the vulnerable script file
    Search for edit_exam1.php in the web root directory. Common paths: /edit_exam1.php, /admin/edit_exam1.php, or /timetabling/edit_exam1.php. Use 'find /var/www -name edit_exam1.php' or similar directory search command.
    Affected if The file edit_exam1.php exists in the web application directory
  3. Inspect ID parameter handling in edit_exam1.php
    Open edit_exam1.php and examine how the 'id' parameter is retrieved (e.g., $_GET['id'], $_POST['id']) and used in SQL queries. Look for direct string concatenation like 'SELECT * FROM table WHERE id=' . $_GET['id'] without escaping or parameter binding.
    Affected if The ID parameter is directly interpolated into SQL queries without prepared statements, escaping, or type casting
  4. Verify database query construction method
    Review the full SQL query execution code in edit_exam1.php. Check if queries use mysqli_prepare(), PDO::prepare(), or parameterized methods. If you see mysql_query(), mysqli_query(), or string concatenation with user input, the vulnerability is present.
    Affected if SQL queries concatenate user-supplied ID parameter values directly without using parameterized queries or input sanitization
  5. Test for SQL injection vulnerability
    With authorization, send a crafted request to edit_exam1.php?id=1' or '1'='1 to observe if the application returns database errors or behaves unexpectedly. Review web server logs and application error logs for SQL syntax errors.
    Affected if The application returns SQL errors, displays unexpected data, or behaves differently when special characters are injected into the ID parameter

You are affected if running SourceCodester Class and Exam Timetabling System version 1.0 with edit_exam1.php present and the ID parameter processed via direct SQL string concatenation instead of parameterized queries.

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 with parameterized queries/prepared statements for the ID parameter, implement strict input validation, and apply least-privilege database access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

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