dbcve.org
LearningApplication · Frappe

CVE-2026-26977

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-20
Fix available
A fix is available. Upgrade to 2.45.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Frappe Learning Management System (LMS) is a learning system that helps users structure their content. In versions 2.44.0 and below, unauthorized users are able to access the details of unpublished courses via API endpoints. A fix for this issue is planned for the 2.45.0 release.

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 confidence

The Frappe LMS versions 2.44.0 and below contain an information disclosure vulnerability where API endpoints for course data do not properly enforce authorization checks. Unpublished courses that should be restricted to authenticated/authorized users can be accessed by any user, including unauthenticated requests, exposing potentially sensitive educational content.

MitigationUpgrade to version 2.45.0 when released. Until then, consider restricting network access to API endpoints or implementing proxy-level authentication controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LearningApplication
Affected:>= 2.0.0, < 2.45.0

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 Frappe Learning is installed
    Check the installed apps in the Frappe bench environment using 'bench get-app list' or review the site's apps list in the Frappe desk under 'Installed Applications'.
    Affected if Frappe Learning appears in the installed applications list
  2. Determine the installed version of Frappe Learning
    Run 'bench list-apps' or check the apps.json file in your Frappe site, or view the app version in the Frappe desk under 'Installed Applications'. Compare the version number against the affected range (>= 2.0.0 and < 2.45.0).
    Affected if The installed version is 2.44.0 or below, or any version from 2.0.0 up to but not including 2.45.0
  3. Verify if course API endpoints are network-accessible
    Attempt to access course-related API endpoints such as /api/method/lms.api.get_courses or /api/method/lms.api.get_course_details from an unauthenticated browser or using a tool like curl without providing authentication headers.
    Affected if The API endpoints respond with HTTP 200 and return course data without requiring authentication
  4. Check for unpublished or restricted courses in the system
    Log into the Frappe desk as an administrator, navigate to the LMS module, and review the course list to identify courses marked as 'Draft', 'Private', or with visibility restrictions.
    Affected if There are unpublished or restricted courses present in the LMS system
  5. Confirm unauthorized access to restricted course content
    Using an unauthenticated request (no login cookies or API token), query specific course API endpoints using course IDs from restricted courses and verify if full course content, lessons, or membership data is returned.
    Affected if Unauthenticated requests successfully retrieve details about courses that should be restricted to authenticated or authorized users only

A system is affected if it runs Frappe Learning version 2.0.0 through 2.44.0 and the course API endpoints are accessible to unauthenticated users, allowing them to view unpublished or restricted course content.

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.

dbcve · scoped
Upgrade available Upgrade to 2.45.0 or later
Fixed in 2.45.0
Interim mitigation

Upgrade to version 2.45.0 when released. Until then, consider restricting network access to API endpoints or implementing proxy-level authentication controls.

Recommended fix High confidence

2.45.0 or later

  1. Back up the current Frappe Learning Management System installation and database
  2. Update the Frappe Learning app to version 2.45.0 or later using bench (e.g., bench get-app [email protected] or bench update)
  3. Migrate the database if required (bench migrate)
  4. Verify the fix by confirming that unauthenticated users can no longer access unpublished courses via API endpoints
  5. Test authenticated users with appropriate permissions can still access unpublished courses they are authorized to view
Caveat Review release notes for 2.45.0 for any potential breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Learning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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