Skip to content

GHSA-8jrv-wx83-w3xj BIT-moodle-2025-67857 CVE-2025-67857

Moodle Inserts Sensitive Information Into Sent Data

Medium Packagist
Severity
4.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.36%
Chance of exploitation in the next 30 days. Higher than 29.52% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-201 Insertion of Sensitive Information Into Sent Data
Fix
4.1.22
Upgrade moodle/moodle to this version or later

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.

Affected versions

Packagist

PackageVulnerableFixed in
moodle/moodle
< 4.1.22
4.1.22
moodle/moodle
>= 4.4.0-beta, < 4.4.12
4.4.12
moodle/moodle
>= 4.5.0-beta, < 4.5.8
4.5.8
moodle/moodle
>= 5.0.0-beta, < 5.0.4
5.0.4
moodle/moodle
>= 5.1.0-beta, < 5.1.1
5.1.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

moodle/moodle Packagist → 4.1.22

composer
composer require moodle/moodle:^4.1.22

Severity breakdown

CVSS 3.1 4.3

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

Weakness

CWE-201: Insertion of Sensitive Information Into Sent Data

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

How to prevent it
  • Requirements: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
  • Implementation: Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
  • System Configuration: Setup default error messages so that unexpected errors do not disclose sensitive information.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-cg8j-5cr2-568q
Moodle TeX formula editor is vulnerable to DoS through lack of execution time limits
Medium Also affects moodle/moodle
GHSA-ggxq-2mg9-8966
Moodle has a Remote Code Execution risk via file restore
High Also affects moodle/moodle
GHSA-hcm6-q6pc-xfhm
Moodle has an authorization logic flaw
Critical Also affects moodle/moodle
GHSA-vwhw-vp9v-q9c9
Moodle vulnerable to Cross-site Scripting
Medium Also affects moodle/moodle
GHSA-5cx4-w4fh-fr57
Moodle Affected by Improper Restriction of Excessive Authentication Attempts
High Also affects moodle/moodle
GHSA-qv78-6gpp-hm68
Moodle Open Redirect vulnerability
Medium Also affects moodle/moodle
GHSA-qfh6-h7j6-fvjv
Moodle formula injection vulnerability
High Also affects moodle/moodle
GHSA-6mmv-f6c6-v6q8
Moodle vulnerable to Cross-site Scripting
Medium Also affects moodle/moodle
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor