CVE-2026-14776
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 Onlne Examination & Learning Management System 1.0. Affected by this vulnerability is the function pathinfo of the file /upload_files.php of the component Filename Extension. Performing a manipulation results in unrestricted upload. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The name of the affected product appears to have a typo in it.
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 confidenceSourceCodester Onlne Examination & Learning Management System 1.0 contains an unrestricted file upload vulnerability in /upload_files.php. The pathinfo function used for filename extension validation fails to properly restrict file types, allowing attackers to upload malicious files (e.g., web shells) to the server. The exploit is publicly available, increasing exploitation risk.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm application installationLocate the file /upload_files.php in the web server's document root (e.g., check paths like /var/www/html/ or C:\inetpub\wwwroot\)Affected if The file /upload_files.php exists in the web root directory
-
Verify product and versionInspect application files or admin panel for version information; compare against version 1.0Affected if The installed version is SourceCodester Online Examination & Learning Management System 1.0
-
Confirm upload functionality is enabledAttempt to access the upload endpoint via HTTP GET request to /upload_files.php or check if the route is registered in the applicationAffected if The upload functionality is accessible and operational
-
Check upload directory locationInspect the application's configuration or source code to determine where uploaded files are stored; verify if the upload directory is within the webrootAffected if Uploaded files are stored inside the publicly accessible web directory
-
Examine file validation logicReview the source code of /upload_files.php to identify use of PHP pathinfo() function for extension validation without additional allowlist controlsAffected if The code uses pathinfo() for extension checking without a strict allowlist or other compensating controls
If SourceCodester Online Examination & Learning Management System version 1.0 is installed with accessible /upload_files.php functionality and uploaded files are stored within the webroot, the environment is likely affected by this unrestricted file upload vulnerability.
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 strict allowlist-based file extension validation combined with MIME type verification and file content analysis. Store uploaded files outside the webroot or rename them to prevent direct execution. Disable script execution in the upload directory.
- 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-14776 — 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-14776 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