How to fix: Sensitive Keywords in HTML Comments
HTML comments containing potentially sensitive information detected.
Why it matters
HTML comments are visible to anyone viewing page source.
Developers often leave TODO notes, debug information, or temporary credentials in HTML comments.
How to fix it
- 1Remove all HTML comments containing sensitive information.
- 2Use a build process that strips comments.
- 3Move debug notes to internal documentation.
Code examples
HTML Minification
const htmlnano = require('htmlnano');
htmlnano.process(html, { removeComments: 'all' });References
Detected automatically by VulnRadar. The check id is sensitive-comments, 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 Keywords in HTML Comments?
- 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-comments, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Sensitive Keywords in HTML Comments map to?
- It maps to CWE-615. 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.