CPE Details
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:a:moodle:moodle:3.9.21:*:*:*:*:*:*:*
Informations
Vendor
moodleProduct
moodleVersion
3.9.21Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| A flaw was found in Moodle. The analysis request action in the Brickfield tool did not include the necessary token to prevent a Cross-site request forgery (CSRF) risk. | 8.8 |
Haute |
||
| A flaw was found in Moodle. When restricting access to a lesson activity with a password, certain passwords could be bypassed or less secure due to a loose comparison in the password-checking logic. This issue only affected passwords set to "magic hash" values. | 5.4 |
Moyen |
||
| A flaw was found in Moodle. Additional checks were required to ensure users can only delete their OAuth2-linked accounts. | 7.5 |
Haute |
||
| A flaw was found in Moodle. Dynamic tables did not enforce capability checks, which resulted in users having the ability to retrieve information they did not have permission to access. | 6.5 |
Moyen |
||
| A vulnerability was found in Moodle. Additional checks are required to ensure users can only access the schedule of a report if they have permission to edit that report. | 4.3 |
Moyen |
||
| A vulnerability was found in Moodle. Users with access to delete audiences from reports could delete audiences from other reports that they do not have permission to delete from. | 6.5 |
Moyen |
||
| A vulnerability was found in Moodle. Additional checks are required to ensure users can only edit or delete RSS feeds that they have permission to modify. | 6.5 |
Moyen |
||
| A vulnerability was found in Moodle. It is possible for users with the "send message" capability to view other users' names that they may not otherwise have access to via an error message in Messaging. Note: The name returned follows the full name format configured on the site. | 4.3 |
Moyen |
||
| A flaw was found in moodle. H5P error messages require additional sanitizing to prevent a reflected cross-site scripting (XSS) risk. | 6.1 |
Moyen |
||
| 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. | 6.1 |
Moyen |
||
| A flaw was found in moodle. Insufficient capability checks make it possible for users with access to restore glossaries in courses to restore them into the global site glossary. | 5.3 |
Moyen |
||
| A flaw was found in moodle. The cURL wrapper in Moodle strips HTTPAUTH and USERPWD headers during emulated redirects, but retains other original request headers, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs. | 5.3 |
Moyen |
||
| A flaw was found in moodle. Some hidden user profile fields are visible in gradebook reports, which could result in users without the "view hidden user fields" capability having access to the information. | 5.3 |
Moyen |
||
| A flaw was found in moodle. When creating an export of site administration presets, some sensitive secrets and keys are not being excluded from the export, which could result in them unintentionally being leaked if the presets are shared with a third party. | 3.7 |
Bas |
||
| A flaw was found in moodle. A local file may include risks when restoring block backups. | 7.5 |
Haute |
||
| The bulk message sending feature in Moodle's Feedback module's non-respondents report had an incorrect CSRF token check, leading to a CSRF vulnerability. | 8.1 |
Haute |
||
| A vulnerability was found in Moodle. Insufficient capability checks made it possible to delete badges that a user does not have permission to access. | 7.5 |
Haute |
||
| To address a cache poisoning risk in Moodle, additional validation for local storage was required. | 7.7 |
Haute |
||
| A flaw was found in Moodle. Additional restrictions are required to avoid a remote code execution risk in calculated question types. Note: This requires the capability to add/update questions. | 8.1 |
Haute |
||
| Incorrect CSRF token checks resulted in multiple CSRF risks. | 8.8 |
Haute |
||
| The cURL wrapper in Moodle retained the original request headers when following redirects, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs. | 7.5 |
Haute |
||
| The site log report required additional encoding of event descriptions to ensure any HTML in the content is displayed in plaintext instead of being rendered. | 4.3 |
Moyen |
||
| In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore database activity modules and direct access to the web server outside of the Moodle webroot could execute a local file include. | 6.5 |
Moyen |
||
| In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore wiki modules and direct access to the web server outside of the Moodle webroot could execute a local file include. | 6.5 |
Moyen |
||
| In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore workshop modules and direct access to the web server outside of the Moodle webroot could execute a local file include. | 5.9 |
Moyen |
||
| In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore feedback modules and direct access to the web server outside of the Moodle webroot could execute a local file include. | 6.5 |
Moyen |
||
| Actions in the admin preset tool did not include the necessary token to prevent a CSRF risk. | 8.4 |
Haute |
||
| ID numbers displayed in the lesson overview report required additional sanitizing to prevent a stored XSS risk. | 4.3 |
Moyen |
||
| Insufficient escaping of participants' names in the participants page table resulted in a stored XSS risk when interacting with some features. | 5.4 |
Moyen |
||
| Additional sanitizing was required when opening the equation editor to prevent a stored XSS risk when editing another user's equation. | 6.1 |
Moyen |
||
| Incorrect validation of allowed event types in a calendar web service made it possible for some users to create events with types/audiences they did not have permission to publish to. | 6.2 |
Moyen |
||
| Inadequate access control in Moodle LMS. This vulnerability could allow a local user with a student role to create arbitrary events intended for users with higher roles. It could also allow the attacker to add events to the calendar of all users without their prior consent. | 6.5 |
Moyen |
||
| Separate Groups mode restrictions were not honoured in the forum summary report, which would display users from other groups. | 3.3 |
Bas |
||
| In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user who also has direct access to the web server outside of the Moodle webroot could utilise a local file include to achieve remote code execution. | 9.8 |
Critique |
||
| Insufficient web service capability checks made it possible to move categories a user had permission to manage, to a parent category they did not have the capability to manage. | 5.3 |
Moyen |
||
| Stronger revision number limitations were required on file serving endpoints to improve cache poisoning protection. | 5.3 |
Moyen |
||
| The course upload preview contained an XSS risk for users uploading unsafe data. | 6.1 |
Moyen |
||
| H5P metadata automatically populated the author with the user's username, which could be sensitive information. | 5.3 |
Moyen |
||
| Wiki comments required additional sanitizing and access restrictions to prevent a stored XSS risk and potential IDOR risk. | 6.5 |
Moyen |
||
| The CSV grade import method contained an XSS risk for users importing the spreadsheet, if it contained unsafe content. | 6.1 |
Moyen |
||
| A remote code execution risk was identified in the IMSCP activity. By default this was only available to teachers and managers. | 8.8 |
Haute |
||
| A remote code execution risk was identified in the Lesson activity. By default this was only available to teachers and managers. | 8.8 |
Haute |
||
| A limited SQL injection risk was identified on the Mnet SSO access control page. This flaw affects Moodle versions 4.2, 4.1 to 4.1.3, 4.0 to 4.0.8, 3.11 to 3.11.14, 3.9 to 3.9.21 and earlier unsupported versions. | 6.3 |
Moyen |
||
| An issue in the logic used to check 0.0.0.0 against the cURL blocked hosts lists resulted in an SSRF risk. This flaw affects Moodle versions 4.2, 4.1 to 4.1.3, 4.0 to 4.0.8, 3.11 to 3.11.14, 3.9 to 3.9.21 and earlier unsupported versions. | 7.5 |
Haute |
||
| It was found in Moodle before version 3.10.1 that some search inputs were vulnerable to reflected XSS due to insufficient escaping of search queries. | 5.4 |
Moyen |
||
| Cross-site scripting (XSS) vulnerability in the Flash component infrastructure in YUI 2.4.0 through 2.8.1, as used in Bugzilla, Moodle, and other products, allows remote attackers to inject arbitrary web script or HTML via vectors related to charts/assets/charts.swf. | 4.3 |
|||
| Cross-site scripting (XSS) vulnerability in the Flash component infrastructure in YUI 2.5.0 through 2.8.1, as used in Bugzilla, Moodle, and other products, allows remote attackers to inject arbitrary web script or HTML via vectors related to uploader/assets/uploader.swf. | 4.3 |
|||
| SQL injection vulnerability in ing/blocks/mrbs/code/web/view_entry.php in the MRBS plugin for Moodle allows remote attackers to execute arbitrary SQL commands via the id parameter. | 7.5 |
