MoodleCMS
CVE-2015-3275
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple cross-site scripting (XSS) vulnerabilities in the SCORM module in Moodle through 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 allow remote attackers to inject arbitrary web script or HTML via a crafted organization name to (1) mod/scorm/player.php or (2) mod/scorm/prereqs.php.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerability in Moodle's SCORM module where the organization name parameter in mod/scorm/player.php and mod/scorm/prereqs.php is not properly sanitized, allowing remote attackers to inject arbitrary JavaScript or HTML via a crafted organization name.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MoodleCMS
<= 2.6.11= 2.7.0= 2.7.1= 2.7.2= 2.7.3= 2.7.4= 2.7.5= 2.7.6= 2.7.7= 2.7.8= 2.7.9= 2.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Moodle versionLocate and inspect the version.php file in the Moodle root directory (typically /version.php or /lib/version.php). Look for the $release or $version variable that declares the installed Moodle version.Affected if The installed version is 2.6.x <= 2.6.11, or 2.7.0 through 2.7.9, or exactly 2.8.0.
-
Verify SCORM module is enabledLog in as administrator and navigate to Site Administration > Plugins > Activity modules > Manage activities, or inspect the mdl_modules database table where name='scorm' and visible=1.Affected if The SCORM activity module is installed and visible/enabled on the site.
-
Inspect SCORM player file for sanitizationOpen mod/scorm/player.php in the Moodle directory and search for code that handles the organization parameter or organization name variable. Check if the code uses proper output escaping functions (such as s(), htmlspecialchars(), or format_string()) when rendering the organization name.Affected if The code in mod/scorm/player.php does not sanitize the organization name parameter before output, allowing unescaped HTML or JavaScript to be rendered.
-
Inspect SCORM prereqs file for sanitizationOpen mod/scorm/prereqs.php and search for code handling the organization parameter or organization name. Verify whether the organization name is passed through sanitization functions before being displayed.Affected if The code in mod/scorm/prereqs.php does not sanitize the organization name parameter before output, allowing unescaped HTML or JavaScript to be rendered.
The environment is affected if the installed Moodle version falls within 2.6.x through 2.6.11, 2.7.0 through 2.7.9, or 2.8.0, AND the SCORM module is enabled, AND the organization name output in mod/scorm/player.php or mod/scorm/prereqs.php lacks proper sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Moodle to version 2.7.9, 2.8.7, 2.9.1 or later to obtain the patched code that properly sanitizes organization name inputs in the SCORM module.
Fix this in Moodle
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3275 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data