MoodleCMS
CVE-2024-45689
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. Dynamic tables did not enforce capability checks, which resulted in users having the ability to retrieve information they did not have permission to access.
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 confidenceMoodle's dynamic tables feature lacks proper capability checks, allowing authenticated users to access information beyond their authorized permissions. This broken access control vulnerability enables users to retrieve sensitive data they should not have visibility into.
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.13>= 4.2.0, < 4.2.10>= 4.3.0, < 4.3.7>= 4.4.0, < 4.4.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Determine the installed Moodle versionLog into Moodle as an administrator and navigate to Site Administration > Server > Environment, or access the /admin/environment.php page. Alternatively, check the version.php file in the Moodle root directory for the $release or $version variable.Affected if The installed version falls within any of these ranges: < 4.1.13, >= 4.2.0 and < 4.2.10, >= 4.3.0 and < 4.3.7, or >= 4.4.0 and < 4.4.3
-
Verify if the dynamic tables feature is accessibleNavigate to any area of Moodle where dynamic tables are used, such as gradebook reports, user listings, or course enrollment pages. As a low-privileged authenticated user (such as a student or guest), attempt to access table views that may contain sensitive information.Affected if A user with limited role capabilities can view or access data tables containing information they should not have permission to see
-
Review user role capability assignmentsGo to Site Administration > Users > Permissions > Define roles and examine the capabilities assigned to each role, particularly focusing on capabilities related to viewing user data, grades, or administrative information.Affected if Roles assigned to standard users (such as student, non-editing teacher) include overly broad data viewing capabilities that bypass expected permission boundaries
-
Check for unauthorized data access via table exportsAs a user with limited permissions, attempt to export or download data from dynamic tables (if export functionality is available) to determine if sensitive information is accessible beyond intended scope.Affected if A low-privileged user can export or view data tables containing information from courses, users, or reports they do not have permission to access
You are affected if your Moodle version is below 4.1.13, between 4.2.0-4.2.10, between 4.3.0-4.3.7, or between 4.4.0-4.4.3 AND users with limited roles can access data beyond their assigned permissions.
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.134.2.104.3.7
Apply the official Moodle security patch or upgrade to the patched version. Review user role capabilities and permissions in the meantime to limit exposure.
Moodle 4.4.3 (or latest stable 4.4.x release)
- 1. Back up your existing Moodle database and moodledata directory before proceeding.
- 2. Download the appropriate fixed Moodle release for your branch: 4.1.13, 4.2.10, 4.3.7, or 4.4.3 (recommended) from moodle.org/downloads.
- 3. Extract the new Moodle files to a temporary location.
- 4. Put your Moodle site into maintenance mode via Site administration > Server > Maintenance mode.
- 5. Replace the old Moodle directory with the new version, preserving your config.php file.
- 6. Run the Moodle upgrade process by accessing the site in a web browser - this will trigger database migrations.
- 7. After successful upgrade, exit maintenance mode.
- 8. Verify that dynamic tables now properly enforce capability checks by testing access controls.
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-2024-45689 — 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-2024-45689 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