dbcve.org
MoodleCMS

CVE-2022-0983

HIGH · 8.8 CVSS v3.1 Published 2022-03-25
Fix available
A fix is available. Upgrade to 3.9.13 / 3.10.10 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An SQL injection risk was identified in Badges code relating to configuring criteria. Access to the relevant capability was limited to teachers and managers by default.

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

SQL injection vulnerability in the Badges component when configuring criteria. Exploitation requires authenticated access with teacher or manager privileges, limiting the attack surface to privileged users within the educational platform.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in the Badges criteria configuration code. Apply input validation and sanitization on all user-supplied parameters.

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.9.0, < 3.9.13>= 3.10.0, < 3.10.10>= 3.11.0, < 3.11.6
FedoraOperating system
Affected:= 35= 36
Extra Packages For Enterprise LinuxApplication
Affected:= 7.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify Moodle installation and version
    Locate the version.php file in the Moodle root directory and read the $release or $version variable, or access Site Administration > Server > Environment to view the installed Moodle version
    Affected if The installed version falls within >= 3.9.0 and < 3.9.13, OR >= 3.10.0 and < 3.10.10, OR >= 3.11.0 and < 3.11.6
  2. Verify the Badges module is enabled
    Navigate to Site Administration > Plugins > Activity modules > Manage activities, or check the Moodle database in the mdl_config table for the 'enablebadges' setting
    Affected if Badges are enabled in the Moodle configuration
  3. Confirm Badges criteria configuration is accessible
    Access the Badges functionality via the navigation: Site Administration > Badges > Add a new badge, or as a teacher navigate to a course and access Badges > Criteria > Add criteria
    Affected if The Badges criteria configuration interface is available to the current user
  4. Check user privilege context
    Review the user account permissions in Site Administration > Users > Permissions > Assign system roles, or for course-level access check the course roles under Course Administration > Users > Enrolled users
    Affected if The account accessing Badge criteria has teacher or manager role privileges

User is affected if running a vulnerable Moodle version within the specified ranges with Badges enabled and possessing teacher or manager privileges that allow accessing the Badges criteria configuration.

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.13 / 3.10.10 / 3.11.6 or later
Fixed in 3.9.133.10.103.11.6
Interim mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements in the Badges criteria configuration code. Apply input validation and sanitization on all user-supplied parameters.

Recommended fix High confidence

Moodle 3.9.13, 3.10.10, or 3.11.6 (minimum fixed versions)

  1. Backup the Moodle database and all site files
  2. Download the fixed Moodle release (3.9.13, 3.10.10, or 3.11.6 depending on your current branch) from moodle.org
  3. Replace the existing Moodle files with the new version files
  4. Run the Moodle upgrade script via command line (php admin/cli/upgrade.php) or through the web interface
  5. Clear the Moodle cache by navigating to Site Administration > Development > Purge caches or running: php admin/cli/purge_caches.php
  6. Verify the Badges functionality works correctly after the upgrade
Caveat Standard Moodle upgrade considerations apply - review the Moodle release notes for your target version for any breaking changes or required migration steps

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

Fix this in Moodle Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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