CVE-2015-0216

CVE-2015-0216 is a low-severity cross-site scripting (XSS) vulnerability in moodle/moodle (composer), affecting versions >= 2.8.0, < 2.8.2. It is fixed in 2.8.2.

Summary

Moodle does not set the RISK_XSS bit for graders

access.php in the Lesson module in Moodle 2.8.x before 2.8.2 does not set the RISK_XSS bit for graders, which allows remote authenticated users to conduct cross-site scripting (XSS) attacks via crafted essay feedback.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

moodle/moodle (>= 2.8.0, < 2.8.2)

Security releases

moodle/moodle → 2.8.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade moodle/moodle to 2.8.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2015-0216? CVE-2015-0216 is a low-severity cross-site scripting (XSS) vulnerability in moodle/moodle (composer), affecting versions >= 2.8.0, < 2.8.2. It is fixed in 2.8.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
  2. Which versions of moodle/moodle are affected by CVE-2015-0216? moodle/moodle (composer) versions >= 2.8.0, < 2.8.2 is affected.
  3. Is there a fix for CVE-2015-0216? Yes. CVE-2015-0216 is fixed in 2.8.2. Upgrade to this version or later.
  4. Is CVE-2015-0216 exploitable, and should I be worried? Whether CVE-2015-0216 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2015-0216 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2015-0216? Upgrade moodle/moodle to 2.8.2 or later.

Other vulnerabilities in moodle/moodle

Stop the waste.
Protect your environment with Kodem.