How to fix: CMS / Technology Fingerprinting
The site exposes CMS or technology stack details that aid attacker reconnaissance.
Why it matters
Knowing the CMS type and version allows attackers to search for specific exploits.
CMS fingerprinting reveals the underlying technology, version, and sometimes plugin information.
How to fix it
- 1Remove or obscure the generator meta tag.
- 2Hide version numbers from public-facing pages.
- 3Keep your CMS and all plugins updated.
- 4Remove default installation files.
Code examples
WordPress
remove_action('wp_head', 'wp_generator');
add_filter('the_generator', '__return_empty_string');References
Detected automatically by VulnRadar. The check id is cms-fingerprinting, 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
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
- MediumSensitive Keywords in HTML Comments
Questions
- How severe is CMS / Technology Fingerprinting?
- VulnRadar rates this info 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 cms-fingerprinting, which stays the same between runs so you can filter, diff, or gate CI on it.
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.