CVE-2025-67847
HIGHCVE-2025-67847 is a high-severity (CVSS 8.8) Code Injection vulnerability in moodle/moodle. O3 Security confirms whether CVE-2025-67847 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Moodle: moodle: remote code execution via insufficient restore input validation
Real-World Exposure
moodle/moodle🐘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. An attacker with access to the restore interface could trigger server-side execution of arbitrary code. This is due to insufficient validation of restore input, which leads to unintended interpretation by core restore routines. Successful exploitation could result in a full compromise of the Moodle application.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | ≥ 5.1.0-beta&&< 5.1.1 | 5.1.1 |
| 🐘Packagist | moodle/moodle | ≥ 5.0.0-beta&&< 5.0.4 | 5.0.4 |
| 🐘Packagist | moodle/moodle | ≥ 4.5.0-beta&&< 4.5.8 | 4.5.8 |
| 🐘Packagist | moodle/moodle | ≥ 4.2.0-beta&&< 4.4.12 | 4.4.12 |
| 🐘Packagist | moodle/moodle | all versions | 4.1.22 |
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 5.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67847 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-2025-67847 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-2025-67847. 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-2025-67847 in your dependencies?
O3 detects CVE-2025-67847 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.