CVE-2026-39405
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. In versions 2.50.0 and below, a user with course editing role could upload a SCORM ZIP package to write files outside the intended directory. This issue has been resolved in version 2.50.1.
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 confidenceFrappe LMS versions 2.50.0 and below contain a path traversal vulnerability in the SCORM ZIP package upload feature. Authenticated users with course editing role can craft malicious ZIP archives containing paths with directory traversal sequences (e.g., ../../../') to write files to arbitrary locations on the server file system, potentially achieving remote code execution.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Frappe LMS installation and versionRun command: bench get-app lms 2>/dev/null || find /home -name 'lms' -type d 2>/dev/null; check version file: cat sites/[sitename]/apps/lms/lms/__init__.py 2>/dev/null | grep __version__Affected if Installed version is 2.50.0 or below (compare against the affected range)
-
Verify SCORM module is enabledAccess Frappe desk: go to Apps > LMS > check if SCORM Player is listed; or query database: SELECT name FROM tabModule WHERE app_name='lms'Affected if SCORM module is present and enabled in the LMS application
-
Confirm course editor role exists and is assignedQuery database: SELECT name, parentrole FROM tabRole WHERE name='Course Editor'; SELECT user_id, role FROM tabUserRole WHERE role='Course Editor'Affected if The Course Editor role exists and is assigned to at least one user
-
Check SCORM upload functionality accessNavigate to: LMS > Courses > Select a course > SCORM Package > Upload; verify if an authenticated user with Course Editor role can access the upload interfaceAffected if SCORM upload interface is accessible to authenticated users with course editor role
Environment is affected if Frappe LMS version is 2.50.0 or below, the SCORM upload feature is enabled, and the Course Editor role is active with assigned users.
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 · scopedUpgrade to Frappe LMS version 2.50.1 or later. If immediate patching is not feasible, restrict the course editing role to trusted users only and implement file system monitoring to detect anomalous write operations.
2.50.1
- 1. Back up your current Frappe Learning Management System installation and database before proceeding.
- 2. Update the Frappe LMS application to version 2.50.1 or later using your Frappe bench manager or by running 'bench get-app lms --overwrite' followed by 'bench --site [site-name] migrate'.
- 3. Verify the update was successful by checking the installed LMS version in your Frappe system.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39405 — 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-39405 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