Skip to content
Fencer Intel
high 7.1

CVE-2025-3625 json

Moodle: user dos and name disclosure via idor in moodle mfa email factor revoke action

published last yr. modified 2mo ago also BIT-moodle-2025-3625 , EUVD-2025-12536

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits
0
none known

Summary

A security vulnerability was discovered in Moodle that can allow hackers to gain access to sensitive information about students and prevent them from logging into their accounts, even after they had completed two-factor authentication (2FA).

Patch / fix

  • bitnami moodle 4.3.12, 4.4.8, 4.5.4
  • moodle moodle 4.3.12, 4.4.8, 4.5.4

Is CVE-2025-3625 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-3625 updated cvss 7.1

moodle: User DoS and Name Disclosure via IDOR in Moodle MFA Email Factor Revoke Action

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
OSV 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami moodle
>=4.3.0, <4.3.12
>=4.4.0, <4.4.8
>=4.5.0, <4.5.4
4.3.12
4.4.8
4.5.4

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.