dbcve.org
MoodleCMS

CVE-2022-30600

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-18
Fix available
A fix is available. Upgrade to 3.9.14 / 3.10.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
A flaw was found in moodle where logic used to count failed login attempts could result in the account lockout threshold being bypassed.

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

A detailed technical summary for this CVE is being prepared.

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:>= 3.9, < 3.9.14>= 3.10, < 3.10.11>= 3.11, < 3.11.7= 4.0.0
Enterprise LinuxOperating system
Affected:= 8.0
FedoraOperating system
Affected:= 34= 35= 36

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 3.9.14 / 3.10.11 / 3.11.7 or later
Fixed in 3.9.143.10.113.11.7
Vendor patch git.moodle.org →
Recommended fix High confidence

Moodle 3.9.14 (for 3.9.x), 3.10.11 (for 3.10.x), 3.11.7 (for 3.11.x), or 4.0.1+ (for 4.0.x)

  1. Identify the currently installed Moodle version by checking the version.php file in the Moodle root directory
  2. Download the appropriate fixed Moodle release from https://download.moodle.org/ based on your current branch (3.9.x, 3.10.x, 3.11.x, or 4.0.x)
  3. Create a complete backup of the Moodle database, Moodle data directory (moodledata), and Moodle code directory
  4. Place the site in maintenance mode via Site Administration > Server > Maintenance Mode
  5. Extract the new Moodle version files, replacing the existing installation while preserving config.php and any custom code in local/ or theme/ directories
  6. Run the upgrade process by accessing the site URL, which will trigger database migrations
  7. Verify the upgrade completed successfully by checking the version number in Site Administration > Server > Environment
  8. Confirm the account lockout functionality works correctly by testing failed login attempts
Caveat Major version upgrades (e.g., 3.11 to 4.0) may require plugin compatibility checks and potential theme updates; minor version upgrades within the same branch are typically low-risk

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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