dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-5546

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-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

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 Campcodes Complete Online Learning Management System 1.0. This impacts the function add_lesson of the file /application/models/Crud_model.php. This manipulation causes unrestricted upload. It is possible to initiate 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

Campcodes Complete Online Learning Management System 1.0 contains an unrestricted file upload vulnerability in the add_lesson function within /application/models/Crud_model.php. The application fails to properly validate file types or contents during upload, allowing remote attackers to upload malicious files that could lead to remote code execution.

MitigationImplement strict file type validation using allowlists, verify file content/magic bytes rather than relying on file extensions, store uploads outside the webroot, and disable script execution in upload directories.

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. Confirm the product installation
    Look for the file /application/models/Crud_model.php in your web server's document root. This file is specific to Campcodes Complete Online Learning Management System.
    Affected if The file /application/models/Crud_model.php exists and belongs to the Campcodes Learning Management System.
  2. Verify the vulnerable version
    Check the application version by reviewing any version file, footer content, or admin panel version display. Compare against version 1.0.
    Affected if The installed version is 1.0 or earlier of Campcodes Complete Online Learning Management System.
  3. Locate the vulnerable function
    Open /application/models/Crud_model.php and search for the function named 'add_lesson' or any function handling lesson file uploads.
    Affected if The add_lesson function exists in Crud_model.php and handles file uploads.
  4. Check file validation in the upload function
    Review the add_lesson function code to see if it validates file types, extensions, or content. Look for any file type whitelist or magic byte checking.
    Affected if The add_lesson function lacks server-side validation of file types and extensions (no whitelist, no MIME type check, no file content validation).
  5. Determine if the upload feature is accessible
    Test if unauthenticated or low-privilege users can access the lesson upload functionality through the web interface. Check router configuration for the add_lesson route.
    Affected if The lesson upload feature is accessible to users without proper admin privileges, or the upload directory is within the web root.
  6. Inspect uploaded files location
    Check the web-accessible directories where uploaded lesson files are stored (commonly in /uploads/ or /assets/ folders within the web root).
    Affected if Uploaded files are stored in a directory accessible via HTTP and script execution is not disabled for that directory.

You are affected if you are running Campcodes Complete Online Learning Management System version 1.0, the add_lesson function in Crud_model.php lacks proper file type validation, and uploaded files are stored in a web-accessible directory with script execution enabled.

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 file type validation using allowlists, verify file content/magic bytes rather than relying on file extensions, store uploads outside the webroot, and disable script execution in upload directories.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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