CVE-2024-48898VulnerabilityPublished 21 Nov 2024

CVE-2024-48898: Missing Authorization

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% 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:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: 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: 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 21 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

AI-suggested

To mitigate CVE-2024-48898, organizations should first verify if their Moodle installations are running affected versions (4.1.0 through 4.4.0). Since no direct patch links were provided, administrators should monitor Moodle's official security advisories and Red Hat's updates for patches addressing this issue. In the interim, implement strict role-based access controls (RBAC) to minimize the number of users with delete permissions on report audiences. Review and audit user permissions regularly to ensure that only trusted personnel have such privileges. Employ monitoring and logging of audience deletion activities to detect any unauthorized or suspicious actions promptly. If possible, restrict deletion capabilities to higher-trust roles or require multi-factor approval workflows for critical actions. Additionally, consider isolating reporting functions or using separate instances for sensitive reports to limit the blast radius of potential exploitation. Educate users about the importance of safeguarding their credentials to prevent insider threats. Finally, plan for timely patch deployment once official fixes are released to fully remediate the vulnerability.

Description

A vulnerability was found in Moodle. Users with access to delete audiences from reports could delete audiences from other reports that they do not have permission to delete from.

Impact

The primary impact of CVE-2024-48898 is on data integrity within Moodle's reporting system. Unauthorized deletion of audiences from reports can lead to inaccurate or incomplete reporting data, potentially affecting decision-making processes in educational or organizational contexts. Since the vulnerability requires authenticated users with some delete permissions, attackers are limited to insiders or compromised accounts, reducing the risk of external exploitation but increasing insider threat concerns. There is no direct impact on confidentiality or availability, so data leakage or service disruption is unlikely. However, the ability to modify report audiences without proper authorization can undermine trust in the system and complicate audit trails. Organizations relying heavily on Moodle for compliance, accreditation, or performance tracking may face operational and reputational risks if this vulnerability is exploited. The lack of known exploits in the wild suggests limited current threat activity, but the ease of exploitation by authorized users means the vulnerability should be addressed promptly to prevent misuse.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 21:47 UTC

Technical details

References

Community reviews

Related threats