CVE-2025-67855VulnerabilityPublished 3 Feb 2026

CVE-2025-67855: mooodle · Cross-site Scripting

Affects mooodleSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium · fixed in 5.1.1 : update mooodle when convenient.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% 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:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: 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: 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 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 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

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Red Hatredhat/mooodle`pkg:rpm/redhat/mooodle`Other threats	Affected =4.1.0 =4.4.0 =4.5.0 =5.0.0 =5.1.0	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

Organizations should immediately verify if their Moodle installations are running affected versions (4.1.0 through 5.1.0) and prioritize upgrading to patched versions once available. In the absence of official patches, administrators should implement input validation and output encoding on URL parameters, especially those used in the policy tool return URL, to neutralize malicious scripts. Employing a Content Security Policy (CSP) can help restrict the execution of unauthorized scripts in browsers. Additionally, educating users about the risks of clicking untrusted links and implementing web application firewalls (WAFs) with rules to detect and block reflected XSS payloads can reduce exploitation likelihood. Monitoring logs for suspicious URL parameters and anomalous user activity can aid in early detection. Regular security assessments and penetration testing focused on web application vulnerabilities should be conducted. Finally, ensure that session cookies are flagged as HttpOnly and Secure to mitigate session theft risks.

Description

A flaw was found in mooodle. A remote attacker could exploit a reflected Cross-Site Scripting (XSS) vulnerability in the policy tool return URL. This vulnerability arises from insufficient sanitization of URL parameters, allowing attackers to inject malicious scripts through specially crafted links. Successful exploitation could lead to information disclosure or arbitrary client-side script execution within the user's browser.

Impact

The primary impact of CVE-2025-67855 is on the confidentiality and integrity of user data within affected Moodle environments. Successful exploitation allows attackers to execute arbitrary scripts in the context of a victim's browser session, potentially leading to session hijacking, theft of authentication tokens, or unauthorized actions performed on behalf of the user. This can result in unauthorized access to sensitive educational records, personal information, or administrative functions. While the vulnerability does not directly affect system availability, the compromise of user accounts can lead to broader security incidents, including privilege escalation or lateral movement if combined with other vulnerabilities. Educational institutions and organizations relying on Moodle for e-learning are particularly at risk, as attackers may target students, educators, or administrators. The requirement for user interaction limits the scope somewhat but does not eliminate risk, especially in phishing-prone environments. The medium CVSS score reflects a moderate risk, but the widespread use of Moodle and the sensitivity of educational data elevate the potential impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats