CVE-2024-48900VulnerabilityPublished 13 Jun 2025

CVE-2024-48900: moodle · Information Exposure

Affects moodleSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 13 Jun 2025
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 2026-10-25.

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

Affected software

Product	Affected	Fixed in
Packagistmoodle/moodle`pkg:composer/moodle/moodle`Other threats	Affected =4.4.0	Fixed in–

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-48900, organizations should first verify and tighten access control policies related to badge recipient visibility within Moodle. Specifically, administrators should audit user roles and permissions to ensure that only authorized users can view badge recipient lists and that these lists are scoped appropriately to prevent overexposure. Until an official patch is released, consider implementing custom code or plugins that enforce stricter checks on badge recipient data access. Monitoring Moodle's official security advisories and promptly applying updates when patches become available is critical. Additionally, organizations should conduct regular access reviews and implement strong authentication and session management to reduce the risk of privilege abuse. Logging and alerting on unusual access patterns to badge recipient data can help detect potential exploitation attempts. Finally, educating users about the sensitivity of badge data and enforcing least privilege principles will further reduce risk.

Description

A vulnerability was found in Moodle. Additional checks are required to ensure users with permission to view badge recipients can only access lists of those they are intended to have access to.

Impact

The primary impact of CVE-2024-48900 is the unauthorized disclosure of sensitive information regarding badge recipients within Moodle. This can lead to privacy violations, as badge recipient lists may contain personally identifiable information or other sensitive data. For educational institutions and organizations using Moodle, this exposure could undermine trust, violate data protection regulations such as GDPR, and potentially expose individuals to targeted social engineering or phishing attacks. Although the vulnerability does not affect system integrity or availability, the confidentiality breach can have reputational and compliance consequences. Since exploitation requires some level of authenticated access, the risk is somewhat mitigated by internal access controls, but insider threats or compromised accounts could leverage this flaw. The scope is limited to Moodle 4.4.0 installations, but given Moodle's global usage, the impact could be widespread in affected environments.

References

bugzilla.redhat.com/show_bug.cgi?id=2318818 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 00:21 UTC

Technical details

References

Community reviews

Related threats