Skip to main content
MediumContentOWASP A05:2021CWE-200

How to fix: Sensitive File References Detected

The page references files commonly associated with sensitive configuration or development artifacts.

Why it matters

References to sensitive files may indicate they are accessible.

Sensitive files like .env, .git/, and configuration files should never be referenced in public pages.

How to fix it

  1. 1Remove all references to sensitive files from public HTML.
  2. 2Block access in your web server configuration.
  3. 3Ensure .env, .git, and other config files are in .gitignore.

Code examples

Nginx

nginx
location ~ /\. { deny all; return 404; }
location ~ \.(env|sql|bak|config|log)$ { deny all; return 404; }

References

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

See every content check

Questions

How severe is Sensitive File References Detected?
VulnRadar rates this medium 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 sensitive-files, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Sensitive File References Detected map to?
It maps to CWE-200. 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 sensitive file references detected

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: Sensitive File References Detected | VulnRadar