CVE-2015-3275: Moodle multiple cross-site scripting (XSS) vulnerabilities
Summary
CVE-2015-3275: Moodle multiple cross-site scripting (XSS) vulnerabilities. Affects moodle/moodle across 3 version ranges.
>= 2.7.0, < 2.7.9
>= 2.8.0, < 2.8.7
>= 2.9.0, < 2.9.1
Fixed in 2.7.9, 2.8.7 or 2.9.1, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Moodle is an open-source learning management system (LMS) used by educational institutions and organizations worldwide. It provides a platform for creating and delivering online courses, managing student enrollment, and facilitating communication between teachers and students. Moodle is written in PHP and utilizes a modular architecture, allowing for the integration of various plugins and modules to extend its functionality. However, multiple cross-site scripting (XSS) vulnerabilities have been identified in the SCORM module of Moodle versions 2.6.11, 2.7.x before 2.7.9, 2.8.x before 2.8.7, and 2.9.x before 2.9.1.
Vulnerability Detail
The identified XSS vulnerabilities in the SCORM module of Moodle allow remote attackers to inject arbitrary web script or HTML by exploiting a flaw in the handling of organization names. Specifically, the vulnerabilities exist in the 'player.php' and 'prereqs.php' files of the SCORM module. An attacker can craft a malicious organization name and submit it to these files, leading to the execution of the injected script or HTML in the context of the affected Moodle instance. This can potentially result in unauthorized access, data theft, or other malicious activities.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 2.7.0, < 2.7.92.7.9composer require moodle/moodle:2.7.9 -
>= 2.8.0, < 2.8.72.8.7composer require moodle/moodle:2.8.7 -
>= 2.9.0, < 2.9.12.9.1composer require moodle/moodle:2.9.1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If upgrading to the latest version is not immediately feasible, a temporary workaround can be implemented by applying input validation and sanitization techniques to the organization name input fields in the 'player.php' and 'prereqs.php' files. This can help prevent the execution of malicious scripts or HTML injected through these fields. Here is an example of how input validation can be implemented in PHP:
$organizationName = $_POST['organization_name'];
// Validate and sanitize the input
if (!empty($organizationName)) {
$sanitizedOrganizationName = htmlspecialchars($organizationName, ENT_QUOTES, 'UTF-8');
// Use the sanitized value in further processing
}
It is important to note that this workaround is not a permanent solution and should be followed by upgrading to the latest patched version as soon as possible.
Conclusion
The identified XSS vulnerabilities in Moodle's SCORM module pose a moderate risk to affected installations. Upgrading to the latest patched versions of Moodle is the recommended solution to address these vulnerabilities. In the meantime, implementing input validation and sanitization techniques can provide a temporary workaround. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for moodle/moodle →
FAQ
Moodle is an open-source learning management system (LMS) used for creating and delivering online courses.
The SCORM module in Moodle allows for the integration of SCORM (Sharable Content Object Reference Model) packages, which are a standard for creating and packaging e-learning content.
Cross-site scripting (XSS) vulnerabilities occur when an application does not properly validate or sanitize user-supplied input, allowing an attacker to inject malicious scripts or HTML into web pages viewed by other users.
The XSS vulnerabilities in Moodle's SCORM module can allow remote attackers to execute arbitrary scripts or HTML in the context of the affected Moodle instance. This can lead to unauthorized access, data theft, or other malicious activities.
To mitigate these vulnerabilities, it is recommended to upgrade to the latest patched versions of Moodle. If immediate upgrading is not possible, implementing input validation and sanitization techniques can serve as a temporary workaround.
References
Related vulnerabilities
Recent vulnerabilities recorded for moodle/moodle.