Cyber Resilience

CVE-2025-62397

Info Disclosure in Moodle 5.0.0 – 5.0.3

Published
23 October 2025
Modified
14 November 2025
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0026 18th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-62397 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Moodle Moodle. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique File and Directory Discovery (T1083); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-11 (Error Handling) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The router’s inconsistent response to invalid course IDs allowed attackers to infer which course IDs exist, potentially aiding reconnaissance.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1595.003 Wordlist Scanning Reconnaissance
Adversaries may iteratively probe infrastructure using brute-forcing and crawling techniques.
Why these techniques?

Inconsistent responses (JSON vs. 404) to invalid course IDs enable enumeration of valid courses and potentially users via timing/response analysis or wordlists, facilitating file/directory discovery analogs, account discovery, and wordlist scanning.

CVEs Like This One

CVE-2024-48896Same product: Moodle Moodle
CVE-2025-62396Same product: Moodle Moodle
CVE-2025-3628Same product: Moodle Moodle
CVE-2025-3645Same product: Moodle Moodle
CVE-2025-3640Same product: Moodle Moodle
CVE-2025-62395Same product: Moodle Moodle
CVE-2025-32044Same product: Moodle Moodle
CVE-2025-3647Same product: Moodle Moodle
CVE-2025-3625Same product: Moodle Moodle
CVE-2025-3627Same product: Moodle Moodle

Affected Assets

moodle
moodle
5.0.0 — 5.0.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-11 Error Handling
  • SI-15 Information Output Filtering
  • AC-4 Information Flow Enforcement
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires systems to handle errors without revealing sensitive internal details such as valid course IDs.

prevent

Filters information in outputs and responses to prevent unauthorized disclosure of existence or validity of identifiers.

prevent

Enforces information flow policies so that responses to invalid inputs do not leak existence information across security boundaries.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

detects

Security testing can detect error messages that leak sensitive information.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error messages.

prevents

Secure SDLC mandates error-handling rules that avoid leaking sensitive information.

prevents

Application security requirements can specify safe error messaging.

prevents

Secure architecture principles include proper exception handling.

References