| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A vulnerability was found in Moodle which exists due to insufficient validation of the HTTP request origin in course redirect URL. A user's CSRF token was unnecessarily included in the URL when being redirected to a course they have just restored. A remote attacker can trick the victim to visit a specially crafted web page and perform arbitrary actions on behalf of the victim on the vulnerable website. This flaw allows an attacker to perform cross-site request forgery attacks. |
| The link to update all installed language packs did not include the necessary token to prevent a CSRF risk. |
| A flaw was found in moodle. Insufficient sanitizing of data when performing a restore could result in a cross-site scripting (XSS) risk from malicious backup files. |
| A flaw was found in moodle. H5P error messages require additional sanitizing to prevent a reflected cross-site scripting (XSS) risk. |
| In Moodle 3.x, students can find out email addresses of other students in the same course. Using search on the Participants page, students could search email addresses of all participants regardless of email visibility. This allows enumerating and guessing emails of other students. |
| In Moodle 2.x and 3.x, searching of arbitrary blogs is possible because a capability check is missing. |
| In Moodle 2.x and 3.x, a CSRF attack is possible that allows attackers to change the "number of courses displayed in the course overview block" configuration setting. |
| In Moodle 2.x and 3.x, web service tokens are not invalidated when the user password is changed or forced to be changed. |
| In Moodle 2.x and 3.x, there is incorrect sanitization of attributes in forums. |
| Cross-site request forgery (CSRF) vulnerability in markposts.php in Moodle 3.0 through 3.0.3, 2.9 through 2.9.5, 2.8 through 2.8.11, 2.7 through 2.7.13 and earlier allows remote attackers to hijack the authentication of users for requests that marks forum posts as read. |
| In Moodle 2.x and 3.x, text injection can occur in email headers, potentially leading to outbound spam. |
| In Moodle 3.x, there is XSS in the assignment submission page. |
| In Moodle 3.x, course creators are able to change system default settings for courses. |
| In Moodle 2.x and 3.x, SQL injection can occur via user preferences. |
| In Moodle 3.2.x, global search displays user names for unauthenticated users. |
| In Moodle 3.x, glossary search displays entries without checking user permissions to view them. |
| Moodle 3.0 through 3.0.3, 2.9 through 2.9.5, and 2.8 through 2.8.11 allows remote attackers to obtain the names of hidden forums and forum discussions. |
| The capability check to access other badges in Moodle 3.0 through 3.0.3, 2.9 through 2.9.5, 2.8 through 2.8.11, 2.7 through 2.7.13, and earlier allows remote authenticated users to read the badges of other users. |
| In Moodle 2.x and 3.x, non-admin site managers may accidentally edit admins via web services. |
| In Moodle 2.x and 3.x, the question engine allows access to files that should not be available. |
