CVE-2024-25980VulnerabilityPublished 31 Mar 2024Updated 1 Aug 2024

CVE-2024-25980: fedora · Improper Access Control

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% 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 31 Mar 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-26.

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-25980, organizations should first verify if they are running affected versions (4.2.0, 4.3.0, or the unspecified '0' version) of the platform. Immediate steps include: 1) Applying any available patches or updates from the vendor as soon as they are released. 2) Temporarily disabling or restricting access to the H5P attempts report feature for non-editing teachers until a fix is applied. 3) Reviewing and tightening role-based access controls to ensure that only authorized users have non-editing teacher privileges. 4) Implementing additional monitoring and logging of access to sensitive reports to detect any unauthorized data access attempts. 5) Educating staff about the sensitivity of cross-group data exposure and encouraging prompt reporting of suspicious activity. 6) If feasible, segregate sensitive user data at the database or application layer to provide defense-in-depth beyond application-level controls. These targeted mitigations go beyond generic advice by focusing on role restrictions, feature access control, and proactive monitoring.

Description

Separate Groups mode restrictions were not honored in the H5P attempts report, which would display users from other groups. By default this only provided additional access to non-editing teachers.

Impact

The primary impact of CVE-2024-25980 is unauthorized disclosure of user attempt data across group boundaries, violating confidentiality principles. Although the exposure is limited to non-editing teachers and read-only access, it can lead to privacy concerns, especially in educational environments where student data is sensitive. Attackers or unauthorized users with non-editing teacher privileges could gain insights into other groups’ activities, potentially undermining trust and compliance with data protection regulations such as FERPA or GDPR. The vulnerability does not affect data integrity or system availability, nor does it allow privilege escalation. However, the breach of group isolation could facilitate further social engineering or targeted attacks. Organizations relying heavily on group segregation for data privacy and compliance may face reputational damage and regulatory scrutiny if this vulnerability is exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:50 UTC

Technical details

References

Community reviews

Related threats