Moodle stored XSS in SCORM objectives report
- Exploited
- No known exploitation
- Fix
- Fixed in 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1
- Who is exposed
- Not reported
Summary
Moodle's SCORM objectives report does not properly sanitize objective identifiers, so a remote attacker with a low-privilege account that can upload content can inject a malicious script. When another user views the report, the script runs in that user's browser and could expose sensitive information or perform actions on their behalf.
Written by a model
Original description
A flaw was found in Moodle. Insufficient sanitization of objective identifiers in the SCORM (Sharable Content Object Reference Model) objectives report allows an authenticated user with content upload permissions to inject malicious scripts. When another user views the report, the injected script executes in their browser session, potentially allowing the attacker to access sensitive information or perform unauthorized actions on their behalf.
What to do
Upgrade to a fixed version: 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133064 (Moodle: stored xss in scorm objectives report), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133064 (entry last updated 2026-11-19):
Affected:
- moodle: fixed in 4.5.16; from 5.0.0, fixed in 5.1.0; from 5.1.0, fixed in 5.1.9; from 5.2.0, fixed in 5.2.5; from 5.3.0, fixed in 5.3.1
Fixed versions: 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133064 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133064 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2576522
- https://access.redhat.com/security/cve/CVE-2026-133064
- https://github.com/moodle/moodle/compare/7fc48ba11d90fecc684996cea63defeb0fb13101...70c972e5f2a8958c92c321cb41a43e98e91bf47a
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133064
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133064"}.Affected versions
- moodlefixed in 4.5.16; From 5.0.0 · fixed in 5.1.0; From 5.1.0 · fixed in 5.1.9; From 5.2.0 · fixed in 5.2.5; From 5.3.0 · fixed in 5.3.1
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.6/10CVSS 4.6
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133064 |
| Record | NVD · CVE-2026-133064 |
| Write-ups 1Establishes: Technical detail and context. | |
| Report | bugzilla.redhat.com · show_bug.cgi?id=2576522 |
| Other links 2 | |
| Repository | GitHub · moodle/moodle · compare/7fc48ba11d90fecc684996cea63defeb0fb13101...70c972e5f2a8958c92c321cb41a43e98e91bf47a |
| Link | access.redhat.com · security/cve/CVE-2026-133064 |
Questions about CVE-2026-133064
Is CVE-2026-133064 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133064?
moodle: before 4.5.16; from 5.0.0 before 5.1.0; from 5.1.0 before 5.1.9; from 5.2.0 before 5.2.5; from 5.3.0 before 5.3.1.
Source: cve.now feed data
How do I fix CVE-2026-133064?
Upgrade to a fixed version: 4.5.16, 5.1.0, 5.1.9, 5.2.5, 5.3.1.
Source: cve.now feed data
Related
- CVE-2026-22308Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop
- CVE-2026-22309Stored cross-site scripting in JTL-Shop
- CVE-2026-130158RepoManager: Stored XSS via host-reported package metadata
- CVE-2026-131260Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
- CVE-2026-131258Stored Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
- CVE-2026-59988django-docutils unsafe Docutils defaults allow local file disclosure, SSRF, and stored XSS
No corrections so far. Something wrong on this page? Report an error.