Security fix guide
Server Version Information Leaked
Response headers reveal the web server software and version (e.g., Apache/2.4.51, nginx/1.21.6). This helps attackers identify known vulnerabilities.
Issue ID: SEC-SERVER-VERSION-001
Severity: minor
Impact: Low
Effort: S
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Response headers reveal the web server software and version (e.g., Apache/2.4.51, nginx/1.21.6). This helps attackers identify known vulnerabilities.
Why it matters
Response headers reveal the web server software and version (e.g., Apache/2.4.51, nginx/1.21.6). This helps attackers identify known vulnerabilities. This affects browser trust signals and whether visitors feel safe submitting contact details.
How we detect it
- FreeSiteAudit flags this issue when the rule for SEC-SERVER-VERSION-001 fails and the page evidence points to Http headers.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Configure the web server to suppress version information
- 2For Apache: ServerTokens Prod and ServerSignature Off
- 3For Nginx: server_tokens off
- 4Remove X-Powered-By headers
How to re-check it
- Check response headers and confirm no server version or X-Powered-By is revealed
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.