How to fix: Sensitive Information in Meta Tags
Meta tags that expose sensitive or unnecessary information.
Why it matters
Meta tag contents are visible in page source.
Generator tags reveal exact software versions with known CVEs. CSRF tokens in meta tags are accessible to any script.
How to fix it
- 1Remove generator meta tags in production.
- 2Move CSRF tokens to HTTP-only cookies.
- 3Never store API keys in meta tags.
Code examples
WordPress
remove_action('wp_head', 'wp_generator');References
Detected automatically by VulnRadar. The check id is sensitive-meta-tags, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- 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
Questions
- How severe is Sensitive Information in Meta Tags?
- VulnRadar rates this low 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-meta-tags, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Sensitive Information in Meta Tags 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.