CPE Details
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
CPE Name: cpe:2.3:a:moodle:moodle:4.1.1:*:*:*:*:*:*:*
Informations
Vendor
moodleProduct
moodleVersion
4.1.1Related CVE
| CVE ID | Publié | Description | Score | Gravité |
|---|---|---|---|---|
| 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 |
||
| Incorrect CSRF token checks resulted in multiple CSRF risks. | 8.8 |
Haute |
||
| Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk. | 8.8 |
Haute |
||
| 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). | 5.3 |
Moyen |
||
| The link to update all installed language packs did not include the necessary token to prevent a CSRF risk. | 8.8 |
Haute |
||
| Separate Groups mode restrictions were not honored when performing a forum export, which would export forum data for all groups. By default this only provided additional access to non-editing teachers. | 5.3 |
Moyen |
||
| Separate Groups mode restrictions were not honored in the H5P attempts report, which would display users from other groups. By default this only provided additional access to non-editing teachers. | 5.3 |
Moyen |
||
| The URL parameters accepted by forum search were not limited to the allowed parameters. | 5.3 |
Moyen |
||
| Insufficient file size checks resulted in a denial of service risk in the file picker's unzip functionality. | 7.5 |
Haute |
||
| 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 |
||
| When duplicating a BigBlueButton activity, the original meeting ID was also duplicated instead of using a new ID for the new activity. This could provide unintended access to the original meeting. | 3.3 |
Bas |
||
| 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 |
||
| ID numbers displayed in the quiz grading report required additional sanitizing to prevent a stored XSS risk. | 5.4 |
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 |
||
| Content on the groups page required additional sanitizing to prevent an XSS risk. This flaw affects Moodle versions 4.2, 4.1 to 4.1.3, 4.0 to 4.0.8 and 3.11 to 3.11.14. | 6.1 |
Moyen |
||
| 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 |
||
| The vulnerability was found Moodle which exists because the application allows a user to control path of the older to create in TinyMCE loaders. A remote user can send a specially crafted HTTP request and create arbitrary folders on the system. | 6.5 |
Moyen |
||
| The vulnerability was found Moodle which exists due to insufficient sanitization of user-supplied data in external Wiki method for listing pages. A remote attacker can send a specially crafted request to the affected application and execute limited SQL commands within the application database. | 7.3 |
Haute |
||
| Content output by the database auto-linking filter required additional sanitizing to prevent an XSS risk. | 6.1 |
Moyen |
||
| The course participation report required additional checks to prevent roles being displayed which the user did not have access to view. | 4.3 |
Moyen |
||
| Insufficient validation of profile field availability condition resulted in an SQL injection risk (by default only available to teachers and managers). | 8.8 |
Haute |
||
| Insufficient sanitizing in backup resulted in an arbitrary file read risk. The capability to access this feature is only available to teachers, managers and admins by default. | 6.5 |
Moyen |
||
| If the algebra filter was enabled but not functional (eg the necessary binaries were missing from the server), it presented an XSS risk. | 6.1 |
Moyen |
||
| The Mustache pix helper contained a potential Mustache injection risk if combined with user input (note: This did not appear to be implemented/exploitable anywhere in the core Moodle LMS). | 9.8 |
Critique |
||
| Authenticated users were able to enumerate other users' names via the learning plans page. | 4.3 |
Moyen |
||
| The link to reset all templates of a database activity did not include the necessary token to prevent a CSRF risk. | 8.8 |
Haute |
||
| Insufficient filtering of grade report history made it possible for teachers to access the names of users they could not otherwise access. | 4.3 |
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 |
2025©
tesweb SA
