CVE-2017-2641
CRITICALCVE-2017-2641 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in moodle/moodle. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2017-2641 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Moodle SQL injection via user preferences
Blast Radius
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
In Moodle 2.x and 3.x, SQL injection can occur via user preferences.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | ≥ 2.7&&< 2.7.19 | 2.7.19 |
| 🐘Packagist | moodle/moodle | ≥ 3.0&&< 3.0.9 | 3.0.9 |
| 🐘Packagist | moodle/moodle | ≥ 3.1&&< 3.1.5 | 3.1.5 |
| 🐘Packagist | moodle/moodle | ≥ 3.2&&< 3.2.2 | 3.2.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Moodle 2.x/3.x - SQL Injection
by Marko Belzetski · Apr 6, 2017
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update moodle/moodle to 2.7.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-2641 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 pinpoints whether CVE-2017-2641 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2017-2641. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2017-2641 in your dependencies?
O3 detects CVE-2017-2641 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.