| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| SQL injection vulnerability in blog/edit.php in Moodle 1.6.1 and earlier allows remote attackers to execute arbitrary SQL commands via the format parameter as stored in the $blogEntry variable, which is not properly handled by the insert_record function, which calls _adodb_column_sql in the adodb layer (lib/adodb/adodb-lib.inc.php), which does not convert the data type to an int. |
| Incorrect CSRF token checks resulted in multiple CSRF risks. |
| Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk. |
| In Moodle, ID numbers displayed in the quiz override screens required additional sanitizing to prevent a stored XSS risk. |
| In moodle, ID numbers displayed in the web service token list required additional sanitizing to prevent a stored XSS risk. |
| In Moodle, insufficient capability checks meant message deletions were not limited to the current user. |
| In Moodle, the file repository's URL parsing required additional recursion handling to mitigate the risk of recursion denial of service. |
| In Moodle, in some circumstances, email notifications of messages could have the link back to the original message hidden by HTML, which may pose a phishing risk. |
| In Moodle, Users' names required additional sanitizing in the account confirmation email, to prevent a self-registration phishing risk. |
| In Moodle, ID numbers exported in HTML data formats required additional sanitizing to prevent a local stored XSS risk. |
| In Moodle, insufficient capability checks made it possible to remove other users' calendar URL subscriptions. |
| In Moodle, a remote code execution risk was identified in the Shibboleth authentication plugin. |
| In Moodle, an SQL injection risk was identified in the library fetching a user's enrolled courses. |
| In Moodle, an SQL injection risk was identified in the library fetching a user's recent courses. |
| In Moodle, insufficient redirect handling made it possible to blindly bypass cURL blocked hosts/allowed ports restrictions, resulting in a blind SSRF risk. |
| Content output by the database auto-linking filter required additional sanitizing to prevent an XSS risk. |
| In Moodle, insufficient limitations in some quiz web services made it possible for students to bypass sequential navigation during a quiz attempt. |
| Insufficient checks in a web service made it possible to add comments to the comments block on another user's dashboard when it was not otherwise available (e.g., on their profile page). |
| Insufficient file size checks resulted in a denial of service risk in the file picker's unzip functionality. |
| The URL parameters accepted by forum search were not limited to the allowed parameters. |
