CVE-2020-25703 — moodle
MEDIUMCVE-2020-25703 is a medium-severity (CVSS 5.3) CWE-201 vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in Moodle
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-25703 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
moodle/moodle🐘moodle/moodle🐘moodle/moodle🐘moodle/moodleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The participants table download in Moodle always included user emails, but should have only done so when users' emails are not hidden. Versions affected: 3.9 to 3.9.2, 3.8 to 3.8.5 and 3.7 to 3.7.8. This is fixed in moodle 3.9.3, 3.8.6, 3.7.9, and 3.10.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | ≥ 3.9.0&&< 3.9.3 | 3.9.3composer require moodle/moodle:^3.9.3 |
| 🐘Packagist | moodle/moodle | ≥ 3.8.0&&< 3.8.6 | 3.8.6composer require moodle/moodle:^3.8.6 |
| 🐘Packagist | moodle/moodle | ≥ 3.7.0&&< 3.7.9 | 3.7.9composer require moodle/moodle:^3.7.9 |
| 🐘Packagist | moodle/moodle | ≥ 3.10.0-beta&&< 3.10.0 | 3.10.0composer require moodle/moodle:^3.10.0 |
Affected Products
fedorafedoraprojectmoodlemoodleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moodle/moodle to 3.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-25703 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2020-25703 in your dependencies?
Find it across Packagist, including transitive dependencies.