CVE-2025-67857VulnerabilityPublished 3 Feb 2026

CVE-2025-67857: moodle · Insertion of Sensitive Information Into Sent Data

Affects moodleSource CVE Database V5

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
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: 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: 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 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-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

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 =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 review their Moodle deployment versions and plan upgrades to patched releases once available. If you cannot patch yet, administrators can implement URL filtering or proxy rules to block or sanitize URLs containing user identifiers during anonymous submissions. Configuring Moodle to minimize or disable anonymous submission features temporarily can reduce exposure. Monitoring web server logs for suspicious access patterns to URLs containing user IDs can help detect exploitation attempts. Educating users about the risks of sharing URLs and enforcing strict access controls on submission pages can further mitigate risk. Collaboration with Moodle community forums and security advisories is essential to stay informed about patches or workarounds. Additionally, organizations should conduct privacy impact assessments to understand the implications of this data exposure and adjust policies accordingly.

Description

A flaw was found in moodle. During anonymous assignment submissions, user identifiers were inadvertently exposed in URLs. This data exposure allows unauthorized viewers to see internal user IDs, compromising the intended anonymity and potentially leading to information disclosure.

Impact

The primary impact of CVE-2025-67857 is the compromise of user anonymity and confidentiality within Moodle environments. Exposure of internal user identifiers can lead to privacy violations, undermining trust in the platform, especially in academic settings where anonymous submissions are critical for unbiased grading and feedback. Attackers or unauthorized viewers could use the exposed IDs to correlate user activity, potentially facilitating targeted phishing, social engineering, or further exploitation. Although the vulnerability does not allow data modification or service disruption, the confidentiality breach could have legal and reputational consequences for educational institutions and organizations relying on Moodle. The scope of impact is significant given Moodle's global adoption in schools, universities, and government agencies. The ease of exploitation (no privileges required) increases risk, though user interaction is necessary. The absence of known exploits reduces immediate threat but does not eliminate future risk.

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