CVE-2026-26031
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 · uneditedFrappe Learning Management System (LMS) is a learning system that helps users structure their content. Prior to 2.44.0, security issue was identified in Frappe Learning, where unauthorised users were able to access the full list of enrolled students (by email) in batches. This vulnerability is fixed in 2.44.0.
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 confidenceFrappe LMS prior to version 2.44.0 contains an broken access control vulnerability where unauthenticated or unauthorized users can retrieve the full list of enrolled students including their email addresses through a batched API endpoint.
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>= 2.0.0, < 2.44.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Frappe Learning module is installedCheck your Frappe/ERPNext site for the 'LMS' or 'Learning Management System' module. This can be done via the Frappe Desk: go to Modules > Learning, or query the database table 'tabModule Def' for 'LMS' or 'Frappe Learning'.Affected if The Frappe Learning module is not present in the environment (not applicable).
-
Determine installed version of Frappe LearningQuery the installed apps table. In Frappe, run 'bench get-app Frappe Learning' to check version, or query the 'tabInstalled Application' or 'tabApp' table in the database for the Frappe Learning app and its version field. Alternatively, check the 'apps.txt' file in your site config or the 'requirements.txt' for 'frappe-learning' or 'lms'.Affected if The installed version falls within >= 2.0.0 and < 2.44.0, indicating the vulnerable version range.
-
Verify access to the student enrollment API endpointTest the batched API endpoint for student data. Attempt a GET request to an endpoint like '/api/method/lms.lms.doctype.lms_batch_enrollment.lms_batch_enrollment.get_batch_students' or similar enrollment listing endpoint without authentication. Use a tool like curl: 'curl -X GET https://your-site/api/method/lms.lms.doctype.lms_batch_enrollment.lms_batch_enrollment.get_batch_students' or check if the API responds with student data including email addresses without requiring login.Affected if The API endpoint returns student enrollment data (including email addresses) without authentication or without proper authorization checks.
The environment is affected if Frappe Learning version is between 2.0.0 and 2.43.x (inclusive) and the enrollment API endpoint is accessible without proper authentication, allowing exposure of student email addresses.
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.
dbcve · scoped2.44.0
Upgrade Frappe LMS to version 2.44.0 or later to apply the access control fix.
2.44.0
- Backup your database and application data before proceeding with any upgrade
- Access your Frappe Bench terminal/environment
- Run 'bench get-app learning' to fetch the latest version, or specify the version with 'bench get-app learning https://github.com/frappe/learning --version 2.44.0'
- Run 'bench --site [your-site-name] migrate' to apply database migrations
- Clear cache by running 'bench --site [your-site-name] clear-cache'
- Restart the Frappe workers with 'bench restart'
- Verify the upgrade by checking the Learning app version in the Frappe system
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26031 — 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-26031 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