VulnerabilityPublished 20 Nov 2024Updated 27 Nov 2024

CVE-2024-45690: moodle · idor when deleting oauth2 linked accounts

Affects moodleSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 4.4.3 : patch moodle soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 20 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.3, 4.3.7, 4.2.10 or 4.1.13.

Affected software

Product	Affected	Fixed in
moodle	Affected <4.1.13 >=4.2 <4.2.10 >=4.3 <4.3.7 >=4.4 <4.4.3	Fixed in 4.4.3 4.3.7 4.2.10 4.1.13
GitHubmoodle`pkg:github/moodle`Other threats	Affected <4.1.13 >=4.2 <4.2.10 >=4.3 <4.3.7 >=4.4 <4.4.3	Fixed in 4.1.13 4.2.10 4.3.7 4.4.3

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-45690, organizations should immediately verify and restrict permissions related to OAuth2 account deletion, ensuring that only authenticated users can delete their own linked accounts. If you cannot patch yet, administrators should implement strict access control policies and audit logs to detect unauthorized deletion attempts. Network-level protections such as web application firewalls (WAFs) can be configured to monitor and block suspicious requests targeting OAuth2 account management endpoints. Additionally, organizations should educate users about potential account management anomalies and encourage prompt reporting of access issues. Where possible, temporarily disabling OAuth2 account deletion functionality or requiring additional authentication factors for such actions can reduce risk. Finally, monitoring threat intelligence feeds for exploit developments related to this CVE will help maintain situational awareness.

Description

A flaw was found in Moodle. Additional checks were required to ensure users can only delete their OAuth2-linked accounts.

Impact

The primary impact of CVE-2024-45690 is on the integrity of user accounts within Moodle installations. Unauthorized deletion of OAuth2-linked accounts can lead to loss of linked authentication credentials, potentially locking users out or forcing them to re-establish account connections. This can disrupt user access and degrade trust in the platform's account management. For organizations relying on Moodle for critical educational or training services, such disruptions can affect operational continuity and user experience. Although confidentiality and availability are not directly compromised, the integrity breach can facilitate further attacks if attackers manipulate account linkages to escalate privileges or impersonate users. The ease of exploitation without authentication or user interaction increases the risk of automated or mass exploitation attempts, especially in large Moodle deployments. The lack of known exploits currently limits immediate widespread impact, but the vulnerability remains a significant risk until patched or mitigated.

CWE-276Incorrect Default Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
During installation, installed file permissions are set to allow anyone to modify those files.
Architecture and Design · Operation
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Web Server Logs Tampering (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, 07:02 UTC

WeaknessesCWE-276

Technical details

References

Community reviews

Related threats