How to fix: Directory Listing Appears Enabled
The response contains patterns indicating directory listing is enabled.
Why it matters
Attackers can browse your server's file structure, discovering sensitive files.
Directory listing allows anyone to see all files in a directory when no index file is present.
How to fix it
- 1Disable directory listing in your web server configuration.
- 2Ensure every directory has an index file.
- 3Review exposed directories for sensitive files.
Code examples
Nginx
autoindex off;Apache
Options -IndexesReferences
Detected automatically by VulnRadar. The check id is directory-listing, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
- MediumSensitive Keywords in HTML Comments
Questions
- How severe is Directory Listing Appears Enabled?
- VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id directory-listing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Directory Listing Appears Enabled map to?
- It maps to CWE-548. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.