Unauthorized actions via exposed course-restore CSRF token
Published Nov 23, 2022 · Updated Apr 25, 2025
CSRF in Moodle LMS 3.9.0 through 3.9.17, 3.11.0 through 3.11.10, and 4.0.0 through 4.0.4 allows remote attackers to act as users. The course-restore redirect places the user's CSRF token in its destination URL while insufficiently validating the HTTP request origin. Exploitation requires a logged-in user who has just restored a course to visit an attacker-controlled page; resulting actions remain limited to that user's Moodle privileges.
Summary
What happened
CSRF in Moodle LMS 3.9.0 through 3.9.17, 3.11.0 through 3.11.10, and 4.0.0 through 4.0.4 allows remote attackers to act as users. The course-restore redirect places the user's CSRF token in its destination URL while insufficiently validating the HTTP request origin. Exploitation requires a logged-in user who has just restored a course to visit an attacker-controlled page; resulting actions remain limited to that user's Moodle privileges.
The record
- CVE
- CVE-2022-45149
- Published
- Nov 23, 2022
- Updated
- Apr 25, 2025
- Vendor
- Moodle
- Product
- Moodle LMS
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 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=Fixed in moodle 4.0.5, moodle 3.11.11, moodle 3.9.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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