Skip to main content
HighContentOWASP A05:2021CWE-548

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

  1. 1Disable directory listing in your web server configuration.
  2. 2Ensure every directory has an index file.
  3. 3Review exposed directories for sensitive files.

Code examples

Nginx

nginx
autoindex off;

Apache

APACHE
Options -Indexes

References

Detected automatically by VulnRadar. The check id is directory-listing, stable across every scan so you can filter or diff on it.

See every content check

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.

Propose a checkHow a check is built

Scan your own site for directory listing appears enabled

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Directory Listing Appears Enabled | VulnRadar