Code execution via legacy-backup deserialization
Published Sep 30, 2022 · Updated May 20, 2025
Unsafe deserialization in affected Moodle LMS releases allows attackers to execute code through a crafted Moodle 1.9 backup. The convert_configdata() method in blocks/html/backup/moodle1/lib.php decodes attacker-controlled configdata and passes the serialized object to PHP unserialize(). Processing the crafted file through a permission-controlled course restore is required; successful exploitation runs attacker-supplied code in the Moodle server process.
Summary
What happened
Unsafe deserialization in affected Moodle LMS releases allows attackers to execute code through a crafted Moodle 1.9 backup. The convert_configdata() method in blocks/html/backup/moodle1/lib.php decodes attacker-controlled configdata and passes the serialized object to PHP unserialize(). Processing the crafted file through a permission-controlled course restore is required; successful exploitation runs attacker-supplied code in the Moodle server process.
The record
- CVE
- CVE-2022-40314
- Published
- Sep 30, 2022
- Updated
- May 20, 2025
- Vendor
- Moodle
- Product
- Moodle LMS
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2022CVE publishedPublication date reported by the CVE source.
- May 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0 to 4.0.3, 3.11 to 3.11.9, 3.9 to 3.9.16 and earlier unsupported versions
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo