VulnerabilityPublished 18 Mar 2019Updated 30 May 2025

CVE-2019-6970: Moodle 3.5.x before 3.5.4 allows SSRF

Source CVE Database V5

Not known to be exploited · fixed in 3.5.4 : patch affected systems soon.

Data as of 26 Oct 2026, 14:05 UTC

Severity

High

Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS: 1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.4

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Mar 2019
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
n/a n/a	Affected <3.5.4	Fixed in 3.5.4

AI-suggested

European organizations using Moodle should immediately verify their Moodle version and upgrade to version 3.5.4 or later where this SSRF vulnerability is patched. If immediate upgrading is not feasible, organizations should implement network-level controls to restrict outbound HTTP requests from the Moodle server to only trusted destinations, minimizing the potential for SSRF exploitation. Web application firewalls (WAFs) can be configured to detect and block suspicious request patterns indicative of SSRF attempts. Additionally, administrators should audit Moodle configurations and logs for unusual outbound requests or access patterns. Segmentation of the Moodle server within the network to limit access to sensitive internal resources can reduce the impact of a successful SSRF attack. Finally, organizations should monitor security advisories from Moodle and related security communities for any emerging exploit information or patches.

Description

Moodle 3.5.x before 3.5.4 allows SSRF.

Impact

For European organizations, particularly educational institutions, universities, and training providers that rely on Moodle, this SSRF vulnerability poses a significant risk. Exploitation could allow attackers to access internal services that are otherwise protected, potentially exposing sensitive student and staff data, internal APIs, or administrative interfaces. This could lead to unauthorized data disclosure, disruption of educational services, or further lateral movement within the organization's network. Given the GDPR regulatory environment in Europe, any data breach resulting from exploitation could also lead to substantial legal and financial consequences. Additionally, since Moodle is often hosted on institutional infrastructure, the SSRF could be used to target internal systems that are not exposed to the internet, increasing the risk of stealthy attacks. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits after vulnerabilities become public.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 15:10 UTC

Technical details

References

Community reviews

Related threats