dbcve.org
MoodleCMS

CVE-2025-3638

HIGH · 8.8 CVSS v3.1 Published 2025-04-25
Fix available
A fix is available. Upgrade to 4.1.18 / 4.3.12 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. The analysis request action in the Brickfield tool did not include the necessary token to prevent a Cross-site request forgery (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 Brickfield accessibility tool where the analysis request action lacks a proper anti-CSRF token. This allows authenticated users to be tricked into submitting unintended analysis requests via malicious links or forms.

MitigationImplement proper CSRF token validation in the Brickfield tool's analysis request action using Moodle's standard form token mechanism.

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.18>= 4.3.0, < 4.3.12>= 4.4.0, < 4.4.8>= 4.5.0, < 4.5.4

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. Identify Moodle version
    Log in as administrator and navigate to Site Administration > Server > Environment, or check the version.php file in the Moodle root directory (look for $version variable). Alternatively, check the footer of any Moodle page for the version number.
    Affected if The installed version falls within < 4.1.18; >= 4.3.0 and < 4.3.12; >= 4.4.0 and < 4.4.8; or >= 4.5.0 and < 4.5.4
  2. Locate Brickfield accessibility tool
    Log in as administrator and navigate to Site Administration > Plugins > Plugins overview, or search for 'Brickfield' in the site administration search bar. The tool may appear under 'Plugins' or as a block/activity module.
    Affected if The Brickfield accessibility tool plugin is installed on the Moodle site
  3. Verify if Brickfield tool is enabled
    Navigate to Site Administration > Plugins > Plugins overview > Filter and search for 'brickfield', or check Site Administration > Plugins > Install plugins to see if Brickfield appears as an installed plugin. Check if there are any Brickfield-related blocks or activities available.
    Affected if The Brickfield accessibility tool is installed and active on the site
  4. Confirm access to analysis request functionality
    Navigate to a course, look for Brickfield accessibility block or menu item if available. The analysis request action is typically found within the Brickfield tool interface where users can request accessibility analysis of course content.
    Affected if The analysis request feature of the Brickfield tool is accessible to authenticated users
  5. Check for missing CSRF token in analysis request
    This requires code inspection: locate the Brickfield analysis request handler file (typically in mod/brickfield or similar path) and verify if the form or action handling the analysis request includes Moodle's standard form token (form::get_token() or $PAGE->request->get_csrf_token()). If the code shows no token validation, the vulnerability exists.
    Affected if The code handling the Brickfield analysis request action does not implement Moodle's standard anti-CSRF token validation

You are affected if your Moodle version is within the affected ranges AND the Brickfield accessibility tool is installed and enabled, with its analysis request feature accessible to authenticated users without proper CSRF protection.

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.18 / 4.3.12 / 4.4.8 or later
Fixed in 4.1.184.3.124.4.8
Interim mitigation

Implement proper CSRF token validation in the Brickfield tool's analysis request action using Moodle's standard form token mechanism.

Recommended fix High confidence

Upgrade to Moodle 4.1.18, 4.3.12, 4.4.8, or 4.5.4 depending on your current branch

  1. 1. Identify the currently installed Moodle version by checking the version.php file in the Moodle root directory
  2. 2. Determine which branch your current version belongs to (4.1.x, 4.3.x, 4.4.x, or 4.5.x)
  3. 3. Download the corresponding fixed version from moodle.org: for 4.1.x use 4.1.18, for 4.3.x use 4.3.12, for 4.4.x use 4.4.8, or for 4.5.x use 4.5.4
  4. 4. Back up the existing Moodle database and code directory before proceeding
  5. 5. Place the site in maintenance mode via Site Administration > Server > Maintenance Mode
  6. 6. Replace the Moodle code directory with the new version files, preserving config.php and any custom plugins
  7. 7. Run the Moodle upgrade process by accessing the site URL, which will trigger the database upgrade
  8. 8. Complete the upgrade and verify the Brickfield tool functionality works correctly
Caveat Standard Moodle upgrade considerations apply - review plugin compatibility and test in staging before production deployment

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-3638 — 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-3638 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