GHSA-m8qh-hx4c-h9hr — moodle/moodle
Fix: moodle/moodle@91e6ad4GHSA-m8qh-hx4c-h9hr is a Cross-Site Request Forgery (CSRF) vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.
Moodle has a CSRF risk in Brickfield tool's analysis request action
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-m8qh-hx4c-h9hr.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
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
A flaw was found in Moodle. The analysis request action in the Brickfield tool did not include the necessary token to prevent a Cross-site request forgery (CSRF) risk.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | all versions | 4.1.18composer require moodle/moodle:^4.1.18 |
| 🐘Packagist | moodle/moodle | ≥ 4.3.0-beta&&< 4.3.12 | 4.3.12composer require moodle/moodle:^4.3.12 |
| 🐘Packagist | moodle/moodle | ≥ 4.4.0-beta&&< 4.4.8 | 4.4.8composer require moodle/moodle:^4.4.8 |
| 🐘Packagist | moodle/moodle | ≥ 4.5.0-beta&&< 4.5.4 | 4.5.4composer require moodle/moodle:^4.5.4 |
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 4.1.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m8qh-hx4c-h9hr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m8qh-hx4c-h9hr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-m8qh-hx4c-h9hr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m8qh-hx4c-h9hr in your dependencies?
O3 Security finds GHSA-m8qh-hx4c-h9hr across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.