MoodleCMS
CVE-2024-43432
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 · uneditedA flaw was found in moodle. The cURL wrapper in Moodle strips HTTPAUTH and USERPWD headers during emulated redirects, but retains other original request headers, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs.
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 confidenceThe cURL wrapper in Moodle incorrectly handles headers during emulated redirects. While it strips HTTPAUTH and USERPWD headers (specific cURL authentication headers), it retains other original request headers including Authorization headers. This causes HTTP authorization credentials to be unintentionally sent to redirect target URLs, potentially leaking authentication information to third-party or malicious destinations.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Check installed Moodle versionLocate and read the version.php file in the /admin/ directory of your Moodle installation. Look for the $release or $version variable. Alternatively, access Site Administration > Server > Environment to view the installed Moodle version.Affected if The installed version falls into any of these ranges: < 4.1.12, >= 4.2.0 and < 4.2.9, >= 4.3.0 and < 4.3.6, or >= 4.4.0 and < 4.4.2
-
Identify if external HTTP requests with authentication are usedReview Moodle plugins or configurations that make outgoing HTTP requests to external services. Check for use of Web services, repository plugins, enrollment plugins, or any custom code that connects to external systems with authentication credentials.Affected if Your Moodle deployment uses any feature that sends authenticated HTTP requests to external URLs that could potentially issue redirects (HTTP 301/302 responses)
-
Inspect cURL wrapper code for header retentionExamine the Moodle cURL wrapper implementation. The vulnerable code is typically in /lib/curl.php or similar cURL utility classes within your Moodle installation. Search for code handling redirect responses that preserves Authorization headers while removing HTTPAUTH/USERPWD headers.Affected if The curl.php file contains redirect-handling logic that explicitly strips certain authentication headers but leaves the Authorization header intact on redirect
Your environment is affected if you run an affected Moodle version (as listed above) AND use any feature that makes authenticated external HTTP requests that may trigger redirects to third-party URLs.
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
Moodle administrators should apply the vendor patch when available. Until then, avoid using Moodle features that involve authenticated requests to external services that may redirect, or implement additional network-level controls to inspect and filter authorization headers on redirect responses.
4.1.12, 4.2.9, 4.3.6, or 4.4.2 (depending on your current branch)
- 1. Determine your current Moodle version by checking the admin interface or config.php file
- 2. Identify which version branch you are on (4.1.x, 4.2.x, 4.3.x, or 4.4.x)
- 3. For Moodle 4.1.x: Upgrade to version 4.1.12 or later
- 4. For Moodle 4.2.x: Upgrade to version 4.2.9 or later
- 5. For Moodle 4.3.x: Upgrade to version 4.3.6 or later
- 6. For Moodle 4.4.x: Upgrade to version 4.4.2 or later
- 7. Before upgrading, back up your Moodle database and codebase
- 8. Review the Moodle upgrade documentation for your specific version jump
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Moodle
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43432 — 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-43432 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