VulnerabilityPublished 4 Feb 2026Updated 26 Feb 2026

CVE-2025-67848: moodle · Improper Handling of Insufficient Permissions or Privileges

Affects moodleSource CVE Database V5

Not known to be exploited · CVSS 8.1 High · fixed in 5.1.1 : patch moodle soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.1High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.1.1, 5.0.4, 4.5.8 +2

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: 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: 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 4 Feb 2026
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 or the CVSS exploit maturity 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

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Packagistmoodle/moodle`pkg:composer/moodle/moodle`Other threats	Affected 4.1.0 – 5.1.0 5 affected builds	Fixed in–
GitHubmoodle`pkg:github/moodle`Other threats	Affected >=4.1.0 <4.1.22 >=4.4.0 <4.4.12 >=4.5.0 <4.5.8 >=5.0.0 <5.0.4 >=5.1.0 <5.1.1	Fixed in 4.1.22 4.4.12 4.5.8 5.0.4 5.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate application of security patches or updates from Moodle once available is the most effective mitigation.
If you cannot patch yet, organizations should disable or restrict the use of the LTI Provider authentication method, especially for suspended users.
Implement additional access control checks at the application or network level to block authentication attempts from suspended accounts.
Monitor authentication logs for unusual login attempts from suspended users and investigate anomalies promptly.
Employ multi-factor authentication (MFA) to add an additional layer of verification, reducing the risk of unauthorized access.
Conduct a thorough review of user suspension and account management policies to ensure proper enforcement.
Educate administrators and users about the vulnerability and encourage prompt reporting of suspicious activities.
Consider network segmentation and limiting external access to Moodle instances to reduce exposure. These steps go beyond generic advice by focusing on specific controls around LTI authentication and suspended user management.

Description

A flaw was found in Moodle. This authentication bypass vulnerability allows suspended users to authenticate through the Learning Tools Interoperability (LTI) Provider. The issue arises from the LTI authentication handlers failing to enforce the user's suspension status, enabling unauthorized access to the system. This can lead to information disclosure or other unauthorized actions by users who should be restricted.

Impact

The vulnerability allows suspended users to regain access to Moodle systems, bypassing intended restrictions. This unauthorized access can lead to significant information disclosure, including access to sensitive student data, course materials, and potentially administrative functions depending on user roles. The integrity of the system is at risk as attackers could perform unauthorized actions such as modifying grades, altering course content, or accessing private communications. The availability impact is minimal as the vulnerability does not directly enable denial-of-service conditions. However, the breach of confidentiality and integrity can severely damage institutional trust, compliance with data protection regulations (e.g., FERPA, GDPR), and the overall security posture of educational organizations. Given Moodle's global adoption in academic institutions, corporate training, and government education programs, the potential impact is widespread and critical.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 07:37 UTC

Technical details

References

Community reviews

Related threats