dbcve.org
MoodleCMS

CVE-2025-62399

HIGH · 7.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 →
84/100
Remediation priority · High
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
Moodle’s mobile and web service authentication endpoints did not sufficiently restrict repeated password attempts, making them susceptible to brute-force attacks.

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 confidence

Moodle's mobile and web service authentication endpoints lack sufficient protection against repeated password attempts, allowing attackers to systematically guess credentials through brute-force attacks. The vulnerability exists in both mobile app and web service authentication mechanisms, enabling automated password spraying without account lockout or rate limiting.

MitigationImplement rate limiting, account lockout policies, and progressive delays after failed authentication attempts on both mobile and web service endpoints. Consider adding CAPTCHA or multi-factor authentication for additional protection.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed Moodle version
    Access the Site Administration > Server > Environment page or check the version.php file in the Moodle root directory. Alternatively, look at the footer of any Moodle admin page which typically displays the version number.
    Affected if The installed version falls within these ranges: 4.1.0 to 4.1.20, 4.4.0 to 4.4.10, 4.5.0 to 4.5.6, or 5.0.0 to 5.0.2.
  2. Verify if web service authentication rate limiting is configured
    Navigate to Site Administration > Plugins > Web services > Manage protocols. Check if there are any rate limiting or throttling settings enabled for the REST or XML-RPC protocols. Inspect the web server configuration (Apache/Nginx) for rate limiting rules applied to /webservice/ endpoints.
    Affected if No rate limiting, throttling, or request rate restrictions are configured on web service authentication endpoints.
  3. Confirm account lockout policy settings
    Navigate to Site Administration > Plugins > Authentication > Manage authentication. Click on the active authentication plugin (such as Manual or LDAP) and verify if account lockout after failed attempts is enabled and configured.
    Affected if Account lockout after failed login attempts is disabled or not configured for the authentication methods used.
  4. Check mobile app authentication protections
    Navigate to Site Administration > Mobile app > Mobile settings. Verify if there are any rate limiting, CAPTCHA requirements, or failed attempt restrictions configured for mobile service authentication endpoints.
    Affected if No rate limiting, progressive delays, or account lockout protections are enforced specifically for mobile app authentication attempts.

A user is affected if their Moodle version is in the affected range AND no rate limiting, account lockout, or progressive delay mechanisms are in place on their web service and mobile authentication endpoints.

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

Implement rate limiting, account lockout policies, and progressive delays after failed authentication attempts on both mobile and web service endpoints. Consider adding CAPTCHA or multi-factor authentication for additional protection.

Recommended fix High confidence

Upgrade to one of: Moodle 4.1.21, 4.4.11, 4.5.7, or 5.0.3 depending on your current branch

  1. 1. Back up your Moodle database and all site files before proceeding
  2. 2. Identify your current Moodle version from Site Administration > Server > PHP info or the admin dashboard
  3. 3. Download the corresponding fixed release: 4.1.21, 4.4.11, 4.5.7, or 5.0.3 from moodle.org/downloads
  4. 4. Replace the Moodle code directory with files from the fixed version, preserving your config.php and any custom themes or plugins
  5. 5. Run the Moodle upgrade script by accessing your site URL (e.g., https://yourmoodle.com) - the system will detect the upgrade and prompt you
  6. 6. Complete the database upgrade when prompted
  7. 7. Clear all caches via Site Administration > Development > Purge caches
  8. 8. Verify the authentication endpoint is now rate-limited by attempting multiple failed password attempts (should be blocked after limited tries)
Caveat Review Moodle release notes for your target version - some plugins or custom code may require updates; test thoroughly in staging first

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

Fix this in Moodle Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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