VulnerabilityPublished 23 Oct 2025

CVE-2025-62396: fedora · Exposure of Information Through Directory Listing

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2025
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

AI-suggested

To mitigate CVE-2025-62396 effectively, organizations should: 1) Immediately review and configure HTTP headers properly to prevent directory listing exposure, ensuring that headers such as 'X-Content-Type-Options' and 'X-Frame-Options' are set securely and that error handling does not reveal directory contents. 2) Disable directory listing at the web server level (e.g., Apache, Nginx) by setting 'Options -Indexes' or equivalent directives to prevent accidental exposure regardless of application behavior. 3) Monitor web server logs for unusual requests that might attempt to exploit directory listing. 4) Apply Moodle patches or updates as soon as they become available from official sources to address the root cause in the router component. 5) Conduct security audits and penetration tests focusing on error handling and information disclosure vectors within Moodle deployments. 6) Employ web application firewalls (WAFs) to detect and block suspicious requests targeting the router script or malformed HTTP headers. These steps go beyond generic advice by focusing on configuration hardening, proactive monitoring, and layered defenses tailored to Moodle's architecture.

Description

An error-handling issue in the Moodle router (r.php) could cause the application to display internal directory listings when specific HTTP headers were not properly configured.

Impact

The primary impact of CVE-2025-62396 is the exposure of internal directory listings, which can provide attackers with sensitive information about the server's file structure and potentially reveal configuration files, scripts, or other resources that could be leveraged in subsequent attacks. While the vulnerability does not directly compromise data integrity or availability, the information disclosure can facilitate more sophisticated attacks such as targeted exploitation, phishing, or privilege escalation. Educational institutions and organizations relying on Moodle for e-learning are at risk of leaking internal system details, which may undermine their security posture. Since the vulnerability requires no authentication and can be exploited remotely, the attack surface is broad. However, the medium severity and lack of known active exploitation reduce immediate critical risk. Still, unpatched systems remain vulnerable to reconnaissance by threat actors, especially in environments where Moodle is widely deployed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 15:49 UTC

Technical details

References

Community reviews

Related threats