dbcve.org
MoodleCMS

CVE-2022-35653

MEDIUM · 6.1 CVSS v3.1 Published 2022-07-25
Fix available
A fix is available. Upgrade to 3.9.15 / 3.11.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Patch available

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 · unedited
A reflected XSS issue was identified in the LTI module of Moodle. The vulnerability exists due to insufficient sanitization of user-supplied data in the LTI module. A remote attacker can trick the victim to follow a specially crafted link and execute arbitrary HTML and script code in user's browser in context of vulnerable website to steal potentially sensitive information, change appearance of the web page, can perform phishing and drive-by-download attacks. This vulnerability does not impact authenticated users.

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
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Affected:>= 3.9.0, < 3.9.15>= 3.11.0, < 3.11.8= 4.0.0= 4.0.1
FedoraOperating system
Affected:= 35= 36
Enterprise LinuxOperating system
Affected:= 8.0

CVSS 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

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.

dbcve · scoped
Upgrade available Upgrade to 3.9.15 / 3.11.8 or later
Fixed in 3.9.153.11.8
Vendor patch git.moodle.org →
Recommended fix High confidence

Moodle 3.9.15, 3.11.8, or 4.0.2 (depending on your current branch)

  1. Identify the currently installed Moodle version using the admin interface or checking the version.php file in the Moodle directory
  2. For Moodle versions 3.9.x (where version >= 3.9.0 and < 3.9.15): Upgrade to Moodle 3.9.15 or later (recommended: 3.9.15)
  3. For Moodle versions 3.11.x (where version >= 3.11.0 and < 3.11.8): Upgrade to Moodle 3.11.8 or later (recommended: 3.11.8)
  4. For Moodle versions 4.0.0 or 4.0.1: Upgrade to Moodle 4.0.2 or later (recommended: 4.0.2)
  5. For Fedora systems: Update the moodle package via 'dnf update moodle' after the vendor releases an updated package
  6. For Enterprise Linux 8 systems: Update the moodle package via 'yum update moodle' after the vendor releases an updated package
  7. After upgrading, verify the LTI module configuration and test that the XSS vulnerability is remediated by attempting to inject script tags in LTI parameters (in a test environment only)
Caveat Review Moodle release notes for your target version to check for any breaking changes; major version jumps (e.g., 3.9 to 4.0) may have significant changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35653 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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