Moodle Stored Cross-site Scripting and page denial of serviceGHSA-jqgr-gh62-jf53
HIGHGHSA-jqgr-gh62-jf53 is a high-severity (CVSS 7.1) Cross-site Scripting (XSS) vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jqgr-gh62-jf53.
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/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
Recursive rendering of Mustache template helpers containing user input could, in some cases, result in an Cross-site Scripting risk or a page failing to load.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | ≥ 3.9&&< 3.9.17 | 3.9.17composer require moodle/moodle:^3.9.17 |
| 🐘Packagist | moodle/moodle | ≥ 3.11&&< 3.11.10 | 3.11.10composer require moodle/moodle:^3.11.10 |
| 🐘Packagist | moodle/moodle | ≥ 4.0&&< 4.0.4 | 4.0.4composer require moodle/moodle:^4.0.4 |
Affected Products
extra packages for enterprise linuxfedoraprojectfedorafedoraprojectmoodlemoodleDetection & 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.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqgr-gh62-jf53 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-jqgr-gh62-jf53 in your dependencies?
Find it across Packagist, including transitive dependencies.