MoodleCMS
CVE-2019-14882
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 vulnerability was found in Moodle 3.7 to 3.7.3, 3.6 to 3.6.7, 3.5 to 3.5.9 and earlier where an open redirect existed in the Lesson edit page.
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 confidenceAn open redirect vulnerability exists in the Lesson edit page of Moodle versions 3.7 to 3.7.3, 3.6 to 3.6.7, 3.5 to 3.5.9 and earlier. The vulnerability allows an attacker to craft a malicious URL containing an arbitrary redirect destination, potentially facilitating phishing attacks by tricking users into visiting malicious sites while believing they are navigating within the legitimate Moodle application.
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.5.0, <= 3.5.9>= 3.6.0, <= 3.6.7>= 3.7.0, <= 3.7.3CVSS 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.
-
Identify Moodle versionNavigate to Site Administration > Server > Environment page or check the version.php file in the Moodle root directory (look for $release or $version variables)Affected if The installed version falls within 3.5.0-3.5.9, 3.6.0-3.6.7, or 3.7.0-3.7.3
-
Verify Lesson module is presentNavigate to Site Administration > Plugins > Activity modules and confirm the Lesson module is installed, or check for mod/lesson directory in the Moodle installationAffected if The Lesson activity module is installed and accessible to users
-
Check Lesson edit page redirect behaviorAccess the Lesson edit page (typically at /mod/lesson/edit.php) and observe if the page accepts a 'returnurl' or 'redirect' parameter that can be manipulated to an external domainAffected if The Lesson edit page permits arbitrary URLs in redirect parameters without validation (requires manual testing in a non-production environment to confirm)
You are affected if your Moodle version is 3.5.0-3.5.9, 3.6.0-3.6.7, or 3.7.0-3.7.3 AND the Lesson activity module is enabled and accessible to potential attackers.
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 the patched versions (3.7.4+, 3.6.8+, 3.5.10+) which contain proper validation of redirect URLs in the Lesson module. Alternatively, implement strict URL validation to ensure redirect targets are relative paths or trusted domains.
Fix this in Moodle
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14882 — 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-2019-14882 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