dbcve.org
MoodleCMS

CVE-2025-62400

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-23
Fix available
A fix is available. Upgrade to 4.1.21 / 4.4.11 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Moodle exposed the names of hidden groups to users who had permission to create calendar events but not to view hidden groups. This could reveal private or restricted group information.

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

Moodle's calendar functionality improperly disclosed hidden group names. Users with calendar event creation permissions but without hidden group view permissions could see the names of hidden groups when creating or viewing calendar events, bypassing the intended access controls for hidden group information.

MitigationApply vendor patch to restrict hidden group name exposure in calendar event handling; verify that users lacking hidden group visibility permissions cannot see hidden group names in any calendar context.

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
Affected:>= 4.1.0, < 4.1.21>= 4.4.0, < 4.4.11>= 4.5.0, < 4.5.7>= 5.0.0, < 5.0.3

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Moodle version
    Navigate to Site administration > Server > System paths or check the version.php file in the Moodle root directory. Run: grep -i '$version' version.php | head -5
    Affected if The installed version falls within: 4.1.0-4.1.20, 4.4.0-4.4.10, 4.5.0-4.5.6, or 5.0.0-5.0.2
  2. Verify calendar event creation capability exists
    Navigate to Site administration > Users > Permissions > Define roles. Check if any role assigned to the target user has 'mod/calendar: Manage entries' or 'mod/calendar: Add entries' capability
    Affected if The user has calendar event creation permissions (mod/calendar: Manage entries or mod/calendar: Add entries)
  3. Confirm user lacks hidden group view permission
    Navigate to Site administration > Users > Permissions > Define roles. Verify the user's role does NOT have 'moodle/site:accessallgroups' capability and is not assigned to any hidden group directly
    Affected if The user does NOT have the 'moodle/site:accessallgroups' capability and is NOT a member of the hidden group
  4. Check for existence of hidden groups
    Navigate to Site administration > Users > Permissions > Groups. Look for groups with 'Hidden' visibility setting. Run SQL: SELECT id, name, visible FROM mdl_groups WHERE visible = 0
    Affected if There are groups configured with visibility set to Hidden in the system
  5. Verify hidden group name disclosure in calendar
    Create a calendar event associated with a hidden group (via event editing, group selection). Then log in as a user WITHOUT hidden group access and view the calendar. Check if the hidden group name appears in the event details
    Affected if A user without hidden group permissions can see the name of a hidden group when viewing or creating calendar events

A user is affected if running a vulnerable Moodle version AND has calendar event creation permissions AND lacks hidden group view permissions AND hidden groups exist in the system, and the hidden group name is visible in the calendar interface.

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 4.1.21 / 4.4.11 / 4.5.7 or later
Fixed in 4.1.214.4.114.5.7
Interim mitigation

Apply vendor patch to restrict hidden group name exposure in calendar event handling; verify that users lacking hidden group visibility permissions cannot see hidden group names in any calendar context.

Recommended fix High confidence

Moodle 4.1.21, 4.4.11, 4.5.7, or 5.0.3 (depending on your current branch)

  1. Backup your Moodle database and all site files
  2. Download the appropriate fixed Moodle version for your branch (4.1.21, 4.4.11, 4.5.7, or 5.0.3) from moodle.org
  3. Place your Moodle site in maintenance mode to prevent user access during upgrade
  4. Replace all Moodle core files with files from the fixed version, preserving your config.php and any customizations in local/ or theme/ directories
  5. Remove the old Moodle directory completely and place the new version in the same location
  6. Ensure the Moodle data directory permissions are correct
  7. Take your site out of maintenance mode
  8. Clear all Moodle caches via Site Administration > Development > Purge caches, or via command line: php admin/cli/purge_caches.php
Caveat Review custom plugins and themes for compatibility with the target version before upgrading; major version jumps may require testing in a staging environment

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

Fix this in Moodle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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