VulnerabilityPublished 23 Oct 2025

CVE-2025-62401: fedora · Improper Authorization

Source CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% 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:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 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 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

1. Apply official patches from Moodle as soon as they become available to address the authorization flaw in the timed assignment feature. 2. Until patches are deployed, consider disabling timed assignments or restricting their use to low-stakes assessments. 3. Implement enhanced monitoring and logging of assignment start and submission times to detect anomalies indicative of time bypass attempts. 4. Enforce strict access controls and multi-factor authentication for student accounts to reduce the risk of account compromise. 5. Conduct regular audits of assessment configurations and student activity logs to identify suspicious behavior. 6. Educate instructors and administrators about the vulnerability and encourage vigilance during exam periods. 7. Explore additional LMS plugins or external proctoring tools that provide stronger timing enforcement and tamper resistance. 8. Review and update incident response plans to include scenarios involving LMS integrity breaches. 9. Coordinate with Moodle community and security advisories to stay informed about updates and exploit developments.

Description

An issue in Moodle’s timed assignment feature allowed students to bypass the time restriction, potentially giving them more time than allowed to complete an assessment.

Impact

The primary impact of CVE-2025-62401 is on the integrity and availability of timed assessments within Moodle. Students exploiting this vulnerability can gain unfair advantages by extending their exam time, potentially invalidating assessment results and undermining academic standards. This can lead to reputational damage for educational institutions and loss of trust in the LMS platform. Additionally, if exploited widely, it could disrupt the scheduling and administration of exams, affecting availability. While confidentiality is not directly impacted, the integrity breach can have downstream effects on grading fairness and certification validity. Organizations relying heavily on Moodle for high-stakes testing or certification programs are particularly at risk. The vulnerability requires authenticated access, so the threat is limited to enrolled students, but insider threat or compromised accounts could exacerbate the risk. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 15:50 UTC

Technical details

References

Community reviews

Related threats