CVE-2024-48901VulnerabilityPublished 21 Nov 2024

CVE-2024-48901: Improper Authorization

Source 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.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:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 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

AI-suggested

To mitigate CVE-2024-48901, organizations should first monitor Moodle's official channels for patches addressing this vulnerability and apply them promptly once available. In the interim, administrators can implement stricter access control policies by reviewing and tightening user permissions related to report editing and scheduling. Custom code or plugins could be used to enforce additional authorization checks ensuring only users with explicit edit rights can access report schedules. Regular audits of user roles and permissions within Moodle can help identify and restrict unnecessary privileges. Network segmentation and monitoring of Moodle server access can reduce the risk of unauthorized exploitation. Additionally, educating users about the importance of safeguarding their credentials and promptly reporting suspicious activity can help mitigate insider threats. Finally, maintaining up-to-date backups of Moodle data ensures recovery options if report schedules are maliciously altered.

Description

A vulnerability was found in Moodle. Additional checks are required to ensure users can only access the schedule of a report if they have permission to edit that report.

Impact

The primary impact of CVE-2024-48901 is on data integrity within Moodle's reporting functionality. Unauthorized users gaining access to report schedules can alter or disrupt the timing and management of reports, potentially causing operational confusion or incorrect reporting outcomes. While confidentiality and availability are not directly affected, the integrity compromise can undermine trust in the system's reporting accuracy. For educational institutions, this could affect grading reports, attendance tracking, or other critical administrative functions. Organizations relying on Moodle for compliance or audit reporting may face challenges if report schedules are manipulated. The requirement for at least some level of privileges limits the scope to authenticated users, but given Moodle's broad user base, this still represents a significant risk. The absence of known exploits reduces immediate threat but does not eliminate the risk of future exploitation. Overall, the vulnerability could lead to unauthorized modifications that impact organizational processes and decision-making based on report data.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

Technical details

References

Community reviews

Related threats