Moodle calculated question type allows remote code execution by Question authorsGHSA-xh2j-q4mc-v522
HIGHGHSA-xh2j-q4mc-v522 is a high-severity (CVSS 8.8) Code Injection vulnerability in moodle/moodle. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for moodle/moodle — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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
An issue was discovered in Moodle 3.x. A Teacher creating a Calculated question can intentionally cause remote code execution on the server, aka eval injection.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | ≥ 3.1&&< 3.1.12 | 3.1.12composer require moodle/moodle:^3.1.12 |
| 🐘Packagist | moodle/moodle | ≥ 3.2&&< 3.2.9 | 3.2.9composer require moodle/moodle:^3.2.9 |
| 🐘Packagist | moodle/moodle | ≥ 3.3&&< 3.3.6 | 3.3.6composer require moodle/moodle:^3.3.6 |
| 🐘Packagist | moodle/moodle | ≥ 3.4&&< 3.4.3 | 3.4.3composer require moodle/moodle:^3.4.3 |
Affected Products
moodlemoodleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Moodle 3.4.1 - Remote Code Execution
by Darryn Ten · Mar 15, 2019
Detection & 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.1.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xh2j-q4mc-v522 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-xh2j-q4mc-v522 in your dependencies?
Find it across Packagist, including transitive dependencies.