CVE-2026-46546
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 version 2.53.0, an authenticated user could supply specially crafted content in certain user-editable fields that, when surfaced in page metadata, caused visitors' browsers to navigate to an attacker-chosen URL. This issue has been patched in version 2.53.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 · high confidenceFrappe LMS versions prior to 2.53.0 contain an open redirect vulnerability where authenticated users can inject specially crafted URLs into user-editable fields. When these fields are rendered in page metadata, visitors' browsers automatically navigate to the attacker-controlled URL.
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.52.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Frappe LMS installationRun 'bench list-apps' or check the sites/[site-name]/apps.txt file to confirm Frappe LMS (also called 'frappe_lms' or 'lms') is installedAffected if Frappe LMS is not listed in the installed apps
-
Determine installed Frappe LMS versionRun 'bench get-app-version frappe_lms' or check the version field in the app's hooks.py or public/js files within the lms app directoryAffected if The version is less than 2.52.0 (e.g., 2.51.0, 2.50.0, etc.)
-
Verify user-editable fields exist in the systemCheck if the LMS has user-editable fields enabled by reviewing the LMS settings or custom fields configuration accessible via 'Frappe > LMS > LMS Settings' or the DocTypes list for Course, Topic, or similar LMS-related DocTypes where user input is storedAffected if User-editable fields for courses, topics, or user profiles are present and allow custom content entry
-
Confirm page metadata rendering of user contentInspect the lms app's web templates (typically in lms/www or lms/templates) for templates that render user-supplied fields into <meta> tags, og:url, or similar metadata elements - look for code that outputs custom field values into page headersAffected if Templates output user-editable field content into page metadata without URL validation
The environment is affected if Frappe LMS version is below 2.52.0 AND user-editable fields from the LMS are being rendered into page metadata, allowing authenticated users to inject malicious URLs that visitor browsers will follow.
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.52.0
Upgrade to Frappe LMS version 2.53.0 or later to patch this vulnerability. Review user-editable fields that populate page metadata to ensure proper URL validation and sanitization are in place.
2.53.0
- Access the Frappe Learning Management System server or environment where the application is deployed
- Locate the Frappe LMS installation directory or deployment configuration
- Pull or fetch the latest version of Frappe LMS
- Update the Frappe LMS package to version 2.53.0 or later using the appropriate package manager (e.g., bench update, pip install, or your deployment method)
- Verify the update was successful by checking the installed version
- Restart any relevant services or application processes to ensure the new version is active
- Test that the application functions correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46546 — 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-46546 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