VulnerabilityPublished 11 Nov 2024Updated 12 Nov 2024

CVE-2024-43427: moodle · admin presets export tool includes some secrets that should not be exported

Affects moodleSource CVE Database V5

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

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

3.7Low

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:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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 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.1.12 >=4.2 <4.2.9 >=4.3 <4.3.6 >=4.4 <4.4.2	Fixed in 4.4.2 4.3.6 4.2.9 4.1.12
Packagistmoodle/moodle`pkg:composer/moodle/moodle`Other threats	Affected =0 =4.2 =4.3 =4.4	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

If you cannot patch yet, organizations should implement the following mitigations: 1) Avoid exporting site administration presets unless absolutely necessary; 2) If export is required, thoroughly review the exported files to identify and remove any sensitive secrets or keys before sharing; 3) Restrict access to exported preset files to trusted personnel only; 4) Implement strict access controls and monitoring around Moodle administrative functions to detect unauthorized export attempts; 5) Regularly audit Moodle configurations and secrets to ensure they are not inadvertently exposed; 6) Stay informed about Moodle security advisories for updates or patches addressing this vulnerability; 7) Consider isolating the Moodle administrative environment to minimize exposure; 8) Educate administrators about the risks of sharing exported presets and enforce policies to prevent accidental leaks.

Description

A flaw was found in moodle. When creating an export of site administration presets, some sensitive secrets and keys are not being excluded from the export, which could result in them unintentionally being leaked if the presets are shared with a third party.

Impact

The primary impact of CVE-2024-43427 is the potential leakage of sensitive secrets and keys contained within Moodle site administration presets. If these presets are shared with unauthorized third parties, attackers could gain access to confidential configuration data, which might facilitate further attacks such as unauthorized access or privilege escalation. However, the vulnerability does not directly allow system compromise, code execution, or denial of service. The scope is limited to confidentiality, and exploitation requires the export and external sharing of presets, which reduces the likelihood of widespread impact. Organizations relying on Moodle for educational or training purposes could face data confidentiality risks, especially if they handle sensitive user or institutional data. The absence of known exploits and the high attack complexity further reduce immediate risk, but the exposure of secrets could have long-term security implications if leveraged by attackers.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (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:26 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats