MoodleCMS
CVE-2025-32045
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 has been identified in Moodle where insufficient capability checks in certain grade reports allowed users without the necessary permissions to access hidden grades.
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 grade reporting functionality contains insufficient capability checks that allow authenticated users without proper permissions to view hidden grades. The vulnerability stems from missing or inadequate permission verifications in certain grade report modules, enabling unauthorized access to grade data that should be concealed.
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.17>= 4.3.0, < 4.3.11>= 4.4.0, < 4.4.7>= 4.5.0, < 4.5.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check installed Moodle versionAccess the Site Administration > Server > Environment page or check the version.php file in the Moodle root directory (look for $version variable). Alternatively, view the footer of any Moodle page which often displays the version.Affected if The installed version falls within: < 4.1.17 OR >= 4.3.0 and < 4.3.11 OR >= 4.4.0 and < 4.4.7 OR >= 4.5.0 and < 4.5.3
-
Identify active grade report modulesNavigate to a course, then go to the gradebook (Grades link). Look for available report types such as 'User report', 'Grade overview', 'Grader report', or 'Single view'. Check which report plugins are enabled in Site Administration > Grades > Grade report setup.Affected if Any grade report module is in use and the Moodle version is unpatched
-
Verify hidden grades configuration existsIn a course gradebook, check if any grades or grade items have visibility set to 'Hidden' (typically done via the eye icon or grade item settings). Note which courses and grade items have hidden grades.Affected if Hidden grades exist in any course and the Moodle instance is running an unpatched version
-
Test unauthorized access to hidden gradesAs an authenticated user without grade editing or administrator privileges, attempt to access grade reports directly via known URLs (such as /grade/report/Grader report or /grade/report/user/index.php) and observe if hidden grades become visible or accessible.Affected if Hidden grade data becomes visible to users who should not have permission to view it (the vulnerability is present)
The environment is affected if running an unpatched Moodle version within the affected ranges AND hidden grades exist AND users without proper grade permissions can access those hidden grades through grade reporting features.
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.174.3.114.4.7
Apply the official Moodle security patch for CVE-2025-32045, which adds proper capability checks to the affected grade report components. After patching, verify that hidden grades are no longer accessible to unauthorized users through direct URL access or report manipulation.
Moodle 4.1.17, 4.3.11, 4.4.7, or 4.5.3 (or later) depending on your current branch
- 1. Identify your current Moodle version in Site Administration > Server > Environment
- 2. Backup your Moodle database and moodledata directory before upgrading
- 3. Upgrade to the appropriate fixed version for your branch: Moodle 4.1.17 (if on 4.1.x), 4.3.11 (if on 4.3.x), 4.4.7 (if on 4.4.x), or 4.5.3 (if on 4.5.x) or later
- 4. Run the Moodle upgrade script via web interface or CLI
- 5. After upgrade, verify that hidden grades are properly protected by reviewing gradebook settings and testing with a non-privileged user account
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Moodle
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32045 — 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-32045 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