MoodleCMS
CVE-2024-43428
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 · uneditedTo address a cache poisoning risk in Moodle, additional validation for local storage was required.
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 confidenceMoodle contained a cache poisoning vulnerability requiring additional validation for local storage. The issue allows attackers to potentially inject malicious data into the cache, affecting subsequent users who receive the poisoned cached content.
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
< 4.1.12>= 4.2.0, < 4.2.9>= 4.3.0, < 4.3.6>= 4.4.0, < 4.4.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Moodle versionLocate the version.php file in your Moodle installation root directory or access the Site Administration > Server > Environment page to view the installed version numberAffected if The version displayed is one of the following: < 4.1.12, >= 4.2.0 but < 4.2.9, >= 4.3.0 but < 4.3.6, or >= 4.4.0 but < 4.4.2
-
Identify if local cache storage is configuredCheck the Moodle configuration for cache settings, typically in config.php or through Site Administration > Plugins > Caching > Cache Stores, to determine if local file-based or internal storage cache drivers are enabledAffected if Local cache storage drivers such as 'file' or 'default' are configured and active on the system
-
Verify cache is being used for user-facing contentReview cache configuration to confirm that local cache stores are serving content to end users, particularly check if cache settings apply to session data or page outputAffected if Local cache is actively serving cached content to users without additional validation layers in place
You are affected if your Moodle version falls within the vulnerable ranges AND local cache storage is enabled and serving content to users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.1.124.2.94.3.6
Apply the Moodle security patch that implements additional validation for local storage to prevent cache poisoning attacks.
Moodle 4.4.2 (or latest in your supported branch: 4.1.12+, 4.2.9+, 4.3.6+)
- Back up your existing Moodle installation and database before proceeding with any upgrade
- Download the fixed Moodle version appropriate for your branch (4.1.12+, 4.2.9+, 4.3.6+, or 4.4.2+) from moodle.org
- Extract the new Moodle files to your server, preserving your config.php and any custom themes or plugins
- Run the Moodle upgrade process via command line (admin/cli/upgrade.php) or through the web interface
- Verify the upgrade completed successfully by logging in and checking the site administration > Server > Environment page
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
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 locallyCheck whether your project pulls in CVE-2024-43428 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-43428 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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