VulnerabilityPublished 11 Nov 2024Updated 12 Nov 2024

CVE-2024-43432: moodle · authorization headers preserved between "emulated redirects

Affects moodleSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 4.4.2 : update moodle when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.4.2, 4.3.6, 4.2.9 +1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade moodle to 4.4.2, 4.3.6, 4.2.9 or 4.1.12.

Affected software

Product	Affected	Fixed in
moodle	Affected >=4.4 <4.4.2	Fixed in 4.4.2
moodle	Affected >=4.3 <4.3.6	Fixed in 4.3.6
moodle	Affected >=4.2 <4.2.9	Fixed in 4.2.9
moodle	Affected <4.1.12	Fixed in 4.1.12
Packagistmoodle/moodle`pkg:composer/moodle/moodle`Other threats	Affected 0 – 4.4 4 affected builds	Fixed in–
GitHubmoodle`pkg:github/moodle`Other threats	Affected <4.1.12 >=4.2 <4.2.9 >=4.3 <4.3.6 >=4.4 <4.4.2	Fixed in 4.1.12 4.2.9 4.3.6 4.4.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-43432, organizations should first apply any official patches or updates released by Moodle addressing this vulnerability once available. In the absence of patches, administrators can implement the following specific measures: 1) Review and restrict the use of HTTP authorization headers in Moodle integrations, avoiding sending sensitive credentials in headers that may be forwarded during redirects. 2) Configure Moodle or underlying cURL options to disable automatic following of redirects or to sanitize headers explicitly during redirects. 3) Employ network-level controls such as web application firewalls (WAFs) to monitor and block suspicious redirect traffic that may leak authorization headers. 4) Audit and limit external redirect URLs to trusted domains only, reducing the risk of credential leakage to malicious endpoints. 5) Educate developers and administrators on secure handling of HTTP headers and redirect behavior in Moodle customizations or plugins. 6) Monitor logs for unusual redirect requests or authorization header exposures. These targeted steps go beyond generic advice by focusing on controlling header transmission during redirects and limiting exposure vectors specific to this vulnerability.

Description

A 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.

Impact

The primary impact of CVE-2024-43432 is the potential unintended disclosure of HTTP authorization header information during HTTP redirects, which can compromise the confidentiality of sensitive credentials or tokens. This leakage could enable attackers to gain unauthorized access to Moodle resources or related systems if they can intercept or control redirect URLs. Although the vulnerability does not affect data integrity or system availability, the exposure of authorization headers can facilitate further attacks such as session hijacking or privilege escalation. Organizations worldwide using affected Moodle versions may face increased risk of credential compromise, especially if their Moodle instances integrate with external services or APIs that rely on HTTP authorization headers. The impact is heightened in environments with sensitive educational data or personal information. Since exploitation does not require authentication or user interaction, attackers can attempt automated reconnaissance and exploitation over the network. However, the absence of known exploits in the wild suggests limited immediate threat but underscores the need for proactive mitigation.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 06:28 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats