CVE-2018-1137:
Moodle Portfolio script allows instantiation of class chosen by user
8.1
CVSS Score
3.0
Basic Information
CVE ID
GHSA ID
EPSS Score
0.64927%
CWE
Published
5/14/2022
Updated
4/23/2024
KEV Status
No
Technology
PHP
PHPTechnical Details
CVSS Vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| moodle/moodle | composer | >= 3.1, < 3.1.12 | 3.1.12 |
| moodle/moodle | composer | >= 3.2, < 3.2.9 | 3.2.9 |
| moodle/moodle | composer | >= 3.3, < 3.3.6 | 3.3.6 |
| moodle/moodle | composer | >= 3.4, < 3.4.3 | 3.4.3 |
Vulnerability Intelligence
Miggo AI
Miggo AIRoot Cause Analysis
The vulnerability stems from improper input validation in portfolio handling code. Moodle's portfolio system allowed user-controlled 'portfolio' parameters to directly determine which class to instantiate. The functions in portfolio/export.php that handle these requests would:
- Accept user-supplied class names via URL parameters
- Instantiate them without verifying if they're valid portfolio classes
- Enable attackers to instantiate arbitrary classes (including non-portfolio classes)
This matches the CWE-20 pattern and explains both the DDoS potential (through resource-intensive class instantiation) and the arbitrary class execution risk. The file paths and function names are consistent with Moodle's portfolio architecture and vulnerability description, though exact implementation details are inferred from security advisory patterns.