dbcve.org
MoodleCMS

CVE-2022-0335

HIGH · 8.8 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 3.9.12 / 3.10.9 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 in versions 3.11 to 3.11.4, 3.10 to 3.10.8, 3.9 to 3.9.11 and earlier unsupported versions. The "delete badge alignment" functionality did not include the necessary token check to prevent a CSRF risk.

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

A CSRF vulnerability exists in Moodle's badge alignment deletion functionality. The delete action lacks proper token validation (sesskey), allowing attackers to craft malicious requests that trick authenticated users into unknowingly deleting badge alignments.

MitigationUpgrade to Moodle versions 3.11.5, 3.10.9, 3.9.12 or later, which include the required token check for the delete badge alignment function.

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:<= 3.8.9>= 3.9.0, < 3.9.12>= 3.10.0, < 3.10.9>= 3.11.0, < 3.11.5

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Check Moodle version from version.php
    Open the file version.php in the Moodle root directory and locate the $release or $version variable to identify the installed version.
    Affected if The version is 3.8.9 or lower, between 3.9.0 and 3.9.11, between 3.10.0 and 3.10.8, or between 3.11.0 and 3.11.4
  2. Verify version via admin interface
    Log in as an administrator and navigate to Site Administration > Server > Environment, or access /admin/environment.php, to view the reported Moodle version.
    Affected if The displayed version matches any of the affected ranges listed above
  3. Confirm badge alignment feature usage
    Navigate to Site Administration > Badges > Manage badges to see if any badges with alignments are defined in the system.
    Affected if Badge alignments exist and users can access the delete alignment function, making them potential targets for the CSRF attack

You are affected if your installed Moodle version falls within any of these ranges: <= 3.8.9, >= 3.9.0 to < 3.9.12, >= 3.10.0 to < 3.10.9, or >= 3.11.0 to < 3.11.5.

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 3.9.12 / 3.10.9 / 3.11.5 or later
Fixed in 3.9.123.10.93.11.5
Interim mitigation

Upgrade to Moodle versions 3.11.5, 3.10.9, 3.9.12 or later, which include the required token check for the delete badge alignment function.

Recommended fix High confidence

Moodle 3.11.5 (or 3.10.9 or 3.9.12 depending on your branch)

  1. 1. Identify the currently installed Moodle version using the site administration or admin/settings.php?section=registration
  2. 2. Determine which upgrade path applies based on current version (3.8.x → 3.8.10+, 3.9.x → 3.9.12+, 3.10.x → 3.10.9+, 3.11.x → 3.11.5+)
  3. 3. Back up the Moodle database and moodledata directory completely
  4. 4. Back up the Moodle source code directory
  5. 5. Download the appropriate fixed version from moodle.org (3.9.12, 3.10.9, or 3.11.5)
  6. 6. Replace the Moodle source code with the new version, preserving config.php and any local customizations
  7. 7. Run the Moodle upgrade script by accessing the site via browser (e.g., yourmoodleurl.com/admin)
  8. 8. Verify the upgrade completed successfully by checking the version in Site Administration > Server > Environment
Caveat Standard Moodle upgrades may have plugin compatibility considerations; verify all third-party plugins have compatible versions for the target release

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

Fix this in Moodle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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