MoodleCMS
CVE-2019-14831
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.1, 3.6 to 3.6.5, 3.5 to 3.5.7 and earlier unsupported versions, where forum subscribe link contained an open redirect if forced subscription mode was enabled. If a forum's subscription mode was set to "forced subscription", the forum's subscribe link contained an open redirect.
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 confidenceAn open redirect vulnerability exists in Moodle's forum module where the subscribe link contains a user-controlled redirect parameter when forced subscription mode is enabled. An attacker could craft a malicious URL to redirect users to an arbitrary site, potentially facilitating phishing attacks.
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.7>= 3.6.0, <= 3.6.5>= 3.7.0, <= 3.7.1CVSS 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.
-
Determine installed Moodle versionLog into the Moodle admin panel and navigate to Site Administration > Server > PHP info to view the version, or inspect the /lib/version.php file in the Moodle directory for the $release variableAffected if The installed version falls within 3.5.0-3.5.7, 3.6.0-3.6.5, or 3.7.0-3.7.1
-
Verify forum module is presentCheck that the mod/forum directory exists in the Moodle installation and the forum module is listed in Site Administration > Plugins > Activity modules > Manage activitiesAffected if Forum module is installed and enabled
-
Review forum subscribe URLs for redirect parametersWhen forced subscription is enabled, navigate to a forum and click the subscribe link. Inspect the URL for a redirect parameter (such as returnurl or redirect) that could be controlled by an attackerAffected if The subscribe URL contains a user-modifiable redirect parameter that redirects to an external site
A user is affected if they run a vulnerable Moodle version (3.5.0-3.5.7, 3.6.0-3.6.5, or 3.7.0-3.7.1) with the forum module enabled and have forced subscription mode activated on any forum activity.
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 version (3.7.2, 3.6.6, 3.5.8 or later). Alternatively, disable forced subscription mode for forums if patching is not immediately feasible.
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-2019-14831 — 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-14831 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