MoodleCMS

CVE-2019-14830

MEDIUM · 6.1 CVSS v3.1 Published 2021-03-19

Fix available

A fix is available. Upgrade to after 3.7.1 or later.

See remediation →

68/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

A 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 the mobile launch endpoint contained an open redirect in some circumstances, which could result in a user's mobile access token being exposed. (Note: This does not affect sites with a forced URL scheme configured, mobile service disabled, or where the mobile app login method is "via the app").

Technical summary

dbcve analysis · high confidence

Open redirect vulnerability in Moodle's mobile launch endpoint allows attackers to redirect users to external sites, potentially exposing mobile access tokens. The vulnerability affects sites with mobile service enabled, no forced URL scheme configured, and login method not set to 'via the app'.

MitigationUpdate Moodle to a patched version (3.7.2+, 3.6.6+, 3.5.8+), or alternatively configure a forced URL scheme, disable the mobile service, or set mobile app login method to 'via the app' as workarounds.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

MoodleCMS

Affected:>= 3.5.0, <= 3.5.7>= 3.6.0, <= 3.6.5>= 3.7.0, <= 3.7.1

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the installed Moodle version

Log into the site as an administrator and navigate to Site administration > Server > System paths, or check the version.php file in the Moodle root directory (look for $version variable).

Affected if The installed version falls within 3.5.0 to 3.5.7, 3.6.0 to 3.6.5, or 3.7.0 to 3.7.1.
Verify if the mobile service is enabled

Navigate to Site administration > Server > Web services > External services. Look for the service named 'Moodle Mobile' or 'Mobile' and confirm whether it is enabled (checkbox is checked).

Affected if The Moodle Mobile service is enabled and the version is in the affected range.
Check if a forced URL scheme is configured

Go to Site administration > Mobile app > Mobile settings. Look for the 'Forced URL scheme' setting. Determine if a value is set (it should be empty or not configured for the vulnerability to apply).

Affected if The 'Forced URL scheme' field is empty or not set, and the mobile service is enabled.
Check the mobile app login method setting

Navigate to Site administration > Mobile app > Mobile settings. Locate the 'Mobile app login method' or 'Authentication method' setting. Determine if it is set to 'via the app' or another value.

Affected if The login method is NOT set to 'via the app' (for example, it is set to 'via browser' or 'embedded'), the mobile service is enabled, and no forced URL scheme is configured.

A user is affected if their Moodle version is in the vulnerable range AND the mobile service is enabled AND no forced URL scheme is configured AND the mobile app login method is not set to 'via the app'.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 3.7.1

Interim mitigation

Update Moodle to a patched version (3.7.2+, 3.6.6+, 3.5.8+), or alternatively configure a forced URL scheme, disable the mobile service, or set mobile app login method to 'via the app' as workarounds.

Fix this in Moodle Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2019-14830 — 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

Primary sources

moodle.orgRelease NotesVendor Advisory
git.moodle.org
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2019-14830?

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.

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

At a glance

A fix existsUpgrade to after 3.7.1 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 3.3%

Affects: Moodle

Remediation

Need this fixed?

Fix this in Moodle 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2019-14830 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References