CVE-2024-48897VulnerabilityPublished 21 Nov 2024

CVE-2024-48897: Improper Authorization

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 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 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-48897, organizations should prioritize applying official patches or updates from Moodle as soon as they become available for versions 4.1.0 through 4.4.0. In the absence of immediate patches, administrators should implement additional authorization checks at the application level to ensure users can only modify or delete RSS feeds they are explicitly permitted to manage. This can include reviewing and tightening role-based access controls (RBAC) and permissions related to RSS feed management. Monitoring and auditing user activities involving RSS feed modifications can help detect unauthorized attempts. Restricting access to Moodle to trusted users and enforcing strong authentication mechanisms will reduce the risk of exploitation. Additionally, educating users about the importance of account security and promptly revoking access for inactive or suspicious accounts will limit potential insider threats. Regular security assessments and code reviews focusing on authorization logic can prevent similar issues in the future.

Description

A vulnerability was found in Moodle. Additional checks are required to ensure users can only edit or delete RSS feeds that they have permission to modify.

Impact

The primary impact of CVE-2024-48897 is on the integrity of Moodle's RSS feed content. Unauthorized users with limited privileges can alter or delete RSS feeds, potentially misleading students, educators, and administrators by modifying course updates or announcements. This can disrupt educational workflows, reduce trust in the platform, and cause confusion. While confidentiality and availability remain unaffected, the integrity compromise can have downstream effects on academic operations and communication. Organizations relying heavily on Moodle for course delivery and communication may experience reputational damage and operational inefficiencies. The vulnerability's exploitation requires authenticated access, limiting exposure to internal or registered users, but insider threats or compromised accounts could leverage this flaw. Since no known exploits are currently in the wild, the immediate risk is moderate, but the vulnerability should be addressed promptly to prevent future exploitation.

References

bugzilla.redhat.com/show_bug.cgi?id=2318821 (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