CVE-2024-45689VulnerabilityPublished 3 Jun 2025

CVE-2024-45689: fedora

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 3 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

AI-suggested

1. Apply official patches or updates from Moodle as soon as they become available to address CVE-2024-45689. Monitor Moodle security advisories and community channels for patch releases. 2. In the absence of patches, implement strict access control reviews to ensure users have the minimum necessary privileges, reducing the risk of exploitation. 3. Conduct thorough audits of user roles and permissions within Moodle to identify and remediate any excessive privileges. 4. Employ network segmentation and monitoring to detect unusual access patterns or data retrieval activities indicative of exploitation attempts. 5. Use web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting dynamic table endpoints. 6. Educate administrators and users about the risk of privilege escalation and encourage strong authentication practices to prevent account compromise. 7. Consider temporary disabling or restricting access to dynamic table features if feasible until patches are applied. 8. Regularly review Moodle logs for anomalous access to sensitive data, enabling early detection of potential exploitation.

Description

A flaw was found in Moodle. Dynamic tables did not enforce capability checks, which resulted in users having the ability to retrieve information they did not have permission to access.

Impact

The primary impact of CVE-2024-45689 is unauthorized disclosure of sensitive information within Moodle environments. This can lead to breaches of student records, grades, personal data, or confidential institutional information. Educational institutions, training providers, and organizations relying on Moodle for e-learning could face privacy violations, regulatory non-compliance (e.g., GDPR), reputational damage, and potential legal consequences. Since the vulnerability requires low privileges, attackers who gain minimal access (such as a registered user or compromised account) can escalate their data access capabilities. Although the vulnerability does not affect data integrity or system availability, the confidentiality breach alone can have severe consequences, especially in environments handling sensitive or regulated data. The lack of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once patches are available or if the vulnerability becomes widely known. Organizations worldwide using affected Moodle versions are at risk, particularly those with large user bases or sensitive data.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 07:01 UTC

Technical details

References

Community reviews

Related threats