dbcve.org
MoodleCMS

CVE-2025-3641

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 →
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
A flaw was found in Moodle. A remote code execution risk was identified in the Moodle LMS Dropbox repository. By default, this was only available to teachers and managers on sites with the Dropbox repository enabled.

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

A remote code execution vulnerability exists in Moodle's Dropbox repository module. By default, teachers and managers with access to the Dropbox repository can potentially execute arbitrary code on the server.

MitigationDisable the Dropbox repository module in Moodle's plugin settings if not required, or apply vendor-supplied patches when available. If the Dropbox integration is needed, restrict user roles and permissions until the fix is applied.

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
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 installed Moodle version
    Access the Site Administration > Server > Environment page or check the version.php file in the Moodle root directory (look for $version variable)
    Affected if Version is < 4.1.18, OR >= 4.3.0 and < 4.3.12, OR >= 4.4.0 and < 4.4.8, OR >= 4.5.0 and < 4.5.4
  2. Confirm Dropbox repository module is installed
    Navigate to Site Administration > Plugins > Repositories > Manage repositories and look for 'Dropbox' in the list of available repository plugins
    Affected if Dropbox repository plugin appears in the list (regardless of enabled/disabled status)
  3. Check if Dropbox repository is enabled
    In the same Manage repositories page, verify whether Dropbox is set to 'Enabled' or 'Disabled'
    Affected if Dropbox repository is enabled and the Moodle version falls within the affected ranges
  4. Identify users with Dropbox repository access
    Go to Site Administration > Users > Permissions > Assign system roles and check which roles (particularly Teacher and Manager roles) have the repository/ Dropbox: view capability
    Affected if Teacher or Manager roles have Dropbox repository access AND the plugin is enabled on an affected version

User is affected if running a vulnerable Moodle version (4.1.x before 4.1.18, 4.3.x before 4.3.12, 4.4.x before 4.4.8, or 4.5.x before 4.5.4) with the Dropbox repository module enabled and accessible to Teacher or Manager role users.

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

Disable the Dropbox repository module in Moodle's plugin settings if not required, or apply vendor-supplied patches when available. If the Dropbox integration is needed, restrict user roles and permissions until the fix is applied.

Recommended fix Moderate confidence

Upgrade to Moodle 4.1.18, 4.3.12, 4.4.8, or 4.5.4 depending on your current version branch (the first fixed release in each branch)

  1. 1. Back up your Moodle database and the moodledata directory before proceeding
  2. 2. Identify your current Moodle version branch (4.1.x, 4.3.x, 4.4.x, or 4.5.x)
  3. 3. Download the appropriate fixed Moodle release from moodle.org (4.1.18, 4.3.12, 4.4.8, or 4.5.4)
  4. 4. Replace your existing Moodle installation files with the new version files
  5. 5. Run the Moodle upgrade process via the command line (php admin/cli/upgrade.php) or through the web interface
  6. 6. Clear all Moodle caches after upgrade completion
  7. 7. Verify the Dropbox repository functionality is working correctly
Caveat Standard Moodle minor version upgrade - review release notes for any deprecated features or behavior changes in your version branch

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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