MoodleCMS
CVE-2020-25702
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 · uneditedIn Moodle, it was possible to include JavaScript when re-naming content bank items. Versions affected: 3.9 to 3.9.2. This is fixed in moodle 3.9.3 and 3.10.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Moodle's content bank feature allows attackers to inject malicious JavaScript code when renaming content bank items. The injected script executes in the browsers of other users who view or interact with the affected content bank items.
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
>= 3.9, < 3.9.3
FedoraOperating system
= 32= 33CVSS 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.1/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.
-
Check Moodle versionAccess the site administration panel or check the version.php file in the Moodle installation directory. The version is typically displayed on the admin dashboard or can be found in /lib/version.php under the $release or $version variables.Affected if The installed version is 3.9, 3.9.1, or 3.9.2 (any version >= 3.9 but earlier than 3.9.3)
-
Verify content bank feature is enabledNavigate to Site Administration > Plugins > Activity modules > Manage activities, or check the 'enabled' status of the content bank module in the database table mdl_modules where name='contentbank'.Affected if The content bank module is present and enabled in the Moodle installation
-
Confirm content bank content existsCheck the database table mdl_contentbank_content for existing records, or attempt to access the content bank through the Moodle UI if you have appropriate permissions.Affected if There are content bank items stored in the database that could contain injected scripts
-
Inspect content bank item names for potential XSS payloadsQuery the mdl_contentbank_content table for any content items with suspicious names containing script tags, javascript:, or other HTML/JS constructs. Run: SELECT id, name, contenttype FROM mdl_contentbank_content WHERE name LIKE '%<%' OR name LIKE '%javascript:%'Affected if Any content bank item names contain unsanitized HTML or JavaScript code
You are affected if your Moodle version is 3.9 through 3.9.2, the content bank feature is enabled, and there are content bank items with unsanitized names containing script tags or JavaScript code.
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 data3.9.3
Upgrade to Moodle 3.9.3 or 3.10 or later to apply the fix that properly sanitizes input during content bank item renaming.
Fix this in Moodle
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25702 — 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-2020-25702 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