-
CVSS Score
-| 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 |
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:
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.
A Semantic Attack on Google Gemini - Read the Latest Research