MoodleCMS
CVE-2025-67848
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 · uneditedA flaw was found in Moodle. This authentication bypass vulnerability allows suspended users to authenticate through the Learning Tools Interoperability (LTI) Provider. The issue arises from the LTI authentication handlers failing to enforce the user's suspension status, enabling unauthorized access to the system. This can lead to information disclosure or other unauthorized actions by users who should be restricted.
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 confidenceMoodle's LTI Provider authentication handlers fail to enforce user suspension status during authentication. When a user attempts to authenticate via LTI (Learning Tools Interoperability), the system does not check whether the user account has been suspended, allowing suspended users to bypass normal authentication controls and gain unauthorized access to the platform.
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
MoodleCMS
< 4.1.22>= 4.4.0, < 4.4.11>= 4.5.0, < 4.5.8>= 5.0.0, < 5.0.4= 5.1.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installed Moodle versionAccess Site Administration > Server > Environment page, or check the version.php file in the Moodle root directory (look for $release or $version variable)Affected if The version is < 4.1.22, OR between 4.4.0-4.4.10, OR between 4.5.0-4.5.7, OR between 5.0.0-5.0.3, OR exactly 5.1.0
-
Verify LTI Provider plugin is enabledNavigate to Site Administration > Plugins > Manage authentication, or check if LTI Provider is listed in Site Administration > Plugins > LTI Provider for institutional enrollmentAffected if LTI Provider authentication is installed and enabled in the Moodle instance
-
Confirm existence of suspended users with LTI accessQuery the mdl_user table for users where suspended=1, then cross-reference with any LTI consumer registrations or roles assigned to those users in the LTI provider interfaceAffected if There are suspended users in the system who have existing LTI consumer registrations or have previously used LTI-based access
-
Inspect LTI authentication handler for suspension validationExamine the file mod/lti/provider/lib.php or auth/lti/auth.php for the user authentication function, specifically looking for checks that validate the user suspended status before establishing a sessionAffected if The LTI authentication handler code does not contain explicit suspension status validation (such as checking user->suspended field or calling user_validate_suspension) prior to authentication completion
A user is affected if their Moodle version falls within the vulnerable ranges AND the LTI Provider plugin is enabled with suspended users who have LTI access potential.
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 · scoped4.1.224.4.114.5.8
Apply the official Moodle security patch when available. Until then, consider disabling or restricting LTI Provider functionality for affected installations and monitor authentication logs for suspicious activity from suspended accounts.
4.1.22 (or later 4.1.x), 4.4.11 (or later 4.4.x), 4.5.8 (or later 4.5.x), 5.0.4 (or later 5.0.x)
- Backup your Moodle database and file system before starting the upgrade process
- Identify your current Moodle version from the administration dashboard (Site administration > Server > Environment or the moodle/about.php page
- For Moodle 4.1.x: Upgrade to version 4.1.22 or later
- For Moodle 4.4.0–4.4.10: Upgrade to version 4.4.11 or later
- For Moodle 4.5.0–4.5.7: Upgrade to version 4.5.8 or later
- For Moodle 5.0.0–5.0.3: Upgrade to version 5.0.4 or later
- After upgrade, verify that suspended users can no longer authenticate via LTI Provider by testing with a suspended test account
- Clear all caches after upgrade (Site administration > Development > Purge caches)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Moodle
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67848 — 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-2025-67848 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