GHSA-mx26-62xm-2p83 — moodle/moodle
HIGHGHSA-mx26-62xm-2p83 is a high-severity (CVSS 7.2) SQL Injection vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.
Moodle vulnerable to site administration SQL injection via XMLDB editor
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-mx26-62xm-2p83.
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.
How urgent is this, really
GHSA-mx26-62xm-2p83 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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 SQL injection risk flaw was found in the XMLDB editor tool available to site administrators.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | all versions | 4.1.12composer require moodle/moodle:^4.1.12 |
| 🐘Packagist | moodle/moodle | ≥ 4.2.0-beta&&< 4.2.9 | 4.2.9composer require moodle/moodle:^4.2.9 |
| 🐘Packagist | moodle/moodle | ≥ 4.3.0-beta&&< 4.3.6 | 4.3.6composer require moodle/moodle:^4.3.6 |
| 🐘Packagist | moodle/moodle | ≥ 4.4.0-beta&&< 4.4.2 | 4.4.2composer require moodle/moodle:^4.4.2 |
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.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mx26-62xm-2p83 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-mx26-62xm-2p83 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mx26-62xm-2p83. 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-mx26-62xm-2p83 in your dependencies?
O3 Security finds GHSA-mx26-62xm-2p83 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.