dbcve.org
MoodleCMS

CVE-2025-26533

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-24
Fix available
A fix is available. Upgrade to 4.1.16 / 4.3.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 the module list filter within course search.

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
How this class of weakness works · CWE-89

User input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.

General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.0, < 4.1.16>= 4.3.0, < 4.3.10>= 4.4.0, < 4.4.6>= 4.5.0, < 4.5.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.16 / 4.3.10 / 4.4.6 or later
Fixed in 4.1.164.3.104.4.6
Vendor patch git.moodle.org →
Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 4.1.16, 4.3.10, 4.4.6, or 4.5.2

  1. 1. Back up your Moodle database and entire Moodle directory (including moodledata) before proceeding
  2. 2. Enable maintenance mode on your Moodle site to prevent user access during upgrade
  3. 3. Download the fixed Moodle version matching your current branch: 4.1.16, 4.3.10, 4.4.6, or 4.5.2
  4. 4. Extract the new Moodle files and replace your existing installation files
  5. 5. If using a customized theme, back up and merge any customizations after core files are updated
  6. 6. Run the Moodle upgrade script by accessing your site in a browser (or run php admin/cli/upgrade.php)
  7. 7. Disable maintenance mode once upgrade completes successfully
  8. 8. Verify the course search functionality works correctly and test the module list filter
Caveat Minor version upgrades typically retain backward compatibility; however, review Moodle release notes for any deprecated features or required database changes before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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