MoodleCMS
CVE-2022-45152
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 · uneditedA blind Server-Side Request Forgery (SSRF) vulnerability was found in Moodle. This flaw exists due to insufficient validation of user-supplied input in LTI provider library. The library does not utilise Moodle's inbuilt cURL helper, which resulted in a blind SSRF risk. An attacker can send a specially crafted HTTP request and trick the application to initiate requests to arbitrary systems. This vulnerability allows a remote attacker to perform SSRF attacks.
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 · moderate confidenceA blind Server-Side Request Forgery vulnerability exists in Moodle's LTI provider library due to insufficient validation of user-supplied input. The vulnerable code makes HTTP requests without using Moodle's built-in cURL helper, allowing remote attackers to trick the application into making arbitrary requests to internal or external systems without seeing the response.
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.18>= 3.11.0, < 3.11.11>= 4.0.0, < 4.0.5
FedoraOperating system
= 35= 36= 37= 7.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 installed Moodle versionLog into Moodle as admin and navigate to Site Administration > Server > System paths, or check the version.php file in the Moodle root directory. Run: grep -i '$version' version.phpAffected if The installed version is < 3.9.18, OR >= 3.11.0 and < 3.11.11, OR >= 4.0.0 and < 4.0.5
-
Verify LTI provider feature statusNavigate to Site Administration > Plugins > Activity modules > LTI provider (or check admin/settings.php?section=modltiprovider). Alternatively, query the database: SELECT * FROM mdl_config WHERE name LIKE '%lti%'Affected if The LTI provider module is installed and enabled in the Moodle instance
-
Identify LTI provider library filesLocate the LTI provider library files in the Moodle codebase. Look for files under mod/lti/provider/ or lib/lti/ that handle outbound HTTP requests. Run: find . -path '*/lti/*' -name '*.php' | xargs grep -l 'file_get_contents\|fopen\|curl_exec' 2>/dev/nullAffected if Custom HTTP request code exists in LTI provider files that bypasses Moodle's built-in cURL helper (check if code uses raw curl or file_get_contents for URLs without going through curl_init-based functions)
You are affected if your Moodle version falls within the affected ranges AND the LTI provider module is enabled with custom HTTP request handling that bypasses Moodle's built-in cURL utilities.
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.
dbcve · scoped3.9.183.11.114.0.5
Remediate by implementing proper input validation and refactoring the LTI provider library to use Moodle's built-in cURL helper with appropriate allowlist/denylist controls to prevent arbitrary URL access.
Moodle 4.0.5 (or latest stable 4.x/3.11.x/3.9.x release matching your branch)
- 1. Back up your current Moodle installation and database before proceeding
- 2. Download the appropriate fixed Moodle version from moodle.org (3.9.18, 3.11.11, or 4.0.5)
- 3. Extract the new Moodle files to your server
- 4. Run the Moodle upgrade process by accessing your site via web browser (e.g., https://yourmoodle.com/admin)
- 5. Follow the on-screen upgrade instructions to complete the update
- 6. Clear all Moodle caches after upgrade (Site Administration > Development > Purge caches)
- 7. Verify the LTI provider functionality works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
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-2022-45152 — 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-2022-45152 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