dbcve.org
MoodleCMS

CVE-2025-67847

HIGH · 8.8 CVSS v3.1 Published 2026-01-23
Fix available
A fix is available. Upgrade to 4.1.22 / 4.4.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. An attacker with access to the restore interface could trigger server-side execution of arbitrary code. This is due to insufficient validation of restore input, which leads to unintended interpretation by core restore routines. Successful exploitation could result in a full compromise of the Moodle application.

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

Moodle's restore functionality contains an input validation flaw that allows authenticated users with restore interface access to inject malicious code that gets executed server-side due to insufficient validation of restore input processed by core restore routines. Successful exploitation enables full compromise of the Moodle application.

MitigationImmediately restrict access to the restore interface to only trusted administrators and monitor for suspicious restore activity. Apply official Moodle security patches when available.

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.22>= 4.4.0, < 4.4.12>= 4.5.0, < 4.5.8>= 5.0.0, < 5.0.4= 5.1.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. Determine your installed Moodle version
    Locate the version.php file in your Moodle root directory and read the $release or $version variable, or access /admin/environment.php via the web interface which displays the installed version
    Affected if The version number is less than 4.1.22, or falls between 4.4.0-4.4.11, 4.5.0-4.5.7, 5.0.0-5.0.3, or equals 5.1.0
  2. Verify if restore functionality is enabled
    Navigate to Site Administration > Courses > Backup > Restore and confirm the restore interface is accessible, or query the mdl_capabilities database table for capability 'moodle/restore:restorecourse'
    Affected if The restore capability exists and is assigned to any role in the system
  3. Identify which roles have restore permissions
    Check Site Administration > Users > Permissions > Define roles for roles that include the 'moodle/restore:restorecourse' capability, or inspect the mdl_role_capabilities table for this capability assignment
    Affected if Any role other than administrator or fully trusted users has been assigned restore permissions
  4. Review recent restore activity logs
    Access Site Administration > Reports > Logs and filter by action 'restore' to identify recent restore operations, or check the mdl_logstore_standard_log table for restore-related events
    Affected if Restore operations have been performed by users outside your trusted administrator group

You are affected if your Moodle version falls within the vulnerable ranges AND the restore interface is accessible to non-administrator 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.22 / 4.4.12 / 4.5.8 or later
Fixed in 4.1.224.4.124.5.8
Interim mitigation

Immediately restrict access to the restore interface to only trusted administrators and monitor for suspicious restore activity. Apply official Moodle security patches when available.

Recommended fix High confidence

Moodle 4.1.22, 4.4.12, 4.5.8, or 5.0.4 depending on your current branch

  1. 1. Back up your current Moodle installation and database before proceeding with any upgrade.
  2. 2. Identify your current Moodle version by checking the admin interface or version.php file.
  3. 3. Download the appropriate patched version for your branch from the official Moodle downloads page (moodle.org).
  4. 4. For Moodle 4.1.x deployments: Upgrade to version 4.1.22.
  5. 5. For Moodle 4.4.x deployments: Upgrade to version 4.4.12.
  6. 6. For Moodle 4.5.x deployments: Upgrade to version 4.5.8.
  7. 7. For Moodle 5.0.x deployments: Upgrade to version 5.0.4.
  8. 8. After upgrading, clear all caches via Site Administration > Development > Purge caches.
Caveat Review Moodle's upgrade documentation for your specific version path; major upgrades between branches may require additional 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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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