dbcve.org
LearningApplication · Frappe

CVE-2023-42807

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-21
Fix available
A fix is available. Upgrade to after 1.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 LMS is an open source learning management system. In versions 1.0.0 and prior, on the People Page of LMS, there was an SQL Injection vulnerability. The issue has been fixed in the `main` branch. Users won't face this issue if they are using the latest main branch of the app.

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

A SQL Injection vulnerability exists in Frappe LMS versions 1.0.0 and prior on the People Page. The vulnerability allows attackers to inject malicious SQL queries through unsanitized input, potentially enabling unauthorized data access, modification, or deletion of the entire database. The issue has been addressed in the main branch.

MitigationUpgrade to the latest main branch of Frappe LMS immediately. The vulnerability is remotely exploitable without authentication, and the CVSS score of 9.8 indicates critical severity requiring urgent remediation.

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:<= 1.0.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
High
Integrity
High
Availability
High

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

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 Frappe LMS installation
    Check your system for Frappe or Frappe Learning packages using your package manager, or look for the 'frappe' or 'lms' directory in your web application root
    Affected if Frappe or Frappe Learning software is present on the system
  2. Determine installed version
    Check the version file or package metadata for Frappe Learning (typically in version.py, __init__.py, or your package manager's installed package info)
    Affected if The installed version is 1.0.0 or any version prior to 1.0.0
  3. Verify People Page is accessible
    Check if the '/people' or '/lms/people' endpoint is enabled in your Frappe LMS configuration and routing setup
    Affected if The People Page endpoint is accessible without authentication (the vulnerability is exploitable without login)
  4. Review application logs for SQL injection indicators
    Search your Frappe/LMS application logs for unusual SQL syntax, error messages containing 'SQL' or 'syntax error', or unexpected database queries to the users or members tables around the People Page
    Affected if Logs show suspicious SQL patterns or database errors originating from People Page requests

You are affected if Frappe Learning version 1.0.0 or earlier is installed and the People Page endpoint is accessible, as the SQL injection vulnerability exists in that specific component.

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 a release after 1.0.0
Interim mitigation

Upgrade to the latest main branch of Frappe LMS immediately. The vulnerability is remotely exploitable without authentication, and the CVSS score of 9.8 indicates critical severity requiring urgent remediation.

Recommended fix Moderate confidence

Latest main branch (post-fix commit)

  1. 1. Ensure you have a full backup of your Frappe LMS instance and database before making any changes.
  2. 2. Navigate to your Frappe LMS application directory.
  3. 3. Pull the latest changes from the main branch using: git pull origin main
  4. 4. Verify the SQL injection vulnerability fix is present by checking the relevant code changes for the People Page.
  5. 5. Clear any application cache if needed.
  6. 6. Test the application to ensure the People Page functionality works correctly after the update.
  7. 7. Monitor logs for any errors following the upgrade.

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

Fix this in Learning Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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