Improper Access ControlWeakness · CWE-284

CVE-2026-14698

MEDIUM · 6.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 →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 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 flaw has been discovered in SourceCodester Syllabus-Aligned Learning Management and Examination System 1.0. Impacted is an unknown function of the file upload_files.php. Performing a manipulation results in unrestricted upload. The attack may 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 · moderate confidence

This is an unrestricted file upload vulnerability in SourceCodester Syllabus-Aligned Learning Management and Examination System 1.0. The upload_files.php script fails to properly validate uploaded file types, allowing attackers to upload malicious files (such as web shells) by manipulating the upload request. This could lead to remote code execution if the uploaded file is accessible via the web server.

MitigationImplement strict server-side file type validation using magic byte checks, whitelist allowed extensions, store uploads outside the web root or disable script execution in the upload directory, and add file size limits.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 if SourceCodester Syllabus-Aligned Learning Management and Examination System is installed
    Look for the application in your web server's document root. Check for directories containing syllabus, learning, examination, or similar LMS-related files.
    Affected if The application is present on the server
  2. Verify the installed version
    Check application files for version information, such as a version.php file, README, or footer/about page. Compare the version to 1.0.
    Affected if The installed version is 1.0
  3. Locate the upload_files.php script
    Search the web directory for upload_files.php using file system inspection or directory enumeration.
    Affected if upload_files.php exists in a web-accessible location
  4. Confirm the upload directory is web-accessible
    Identify the upload directory configured in upload_files.php or in related configuration. Check if this directory is served by the web server and allows direct access to uploaded files.
    Affected if The upload directory is accessible via HTTP/HTTPS and permits script execution (e.g., .php files can be executed)

You are affected if you are running version 1.0 of SourceCodester Syllabus-Aligned Learning Management and Examination System and the upload_files.php script is present and web-accessible with the upload directory allowing script execution.

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 strict server-side file type validation using magic byte checks, whitelist allowed extensions, store uploads outside the web root or disable script execution in the upload directory, and add file size limits.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14698 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