How to fix: X-Powered-By header reveals application framework
The X-Powered-By response header discloses the application framework and sometimes version (e.g., "Express", "PHP/8.1").
Why it matters
Knowing the framework allows attackers to focus on framework-specific vulnerabilities, default paths, and known misconfigurations, reducing reconnaissance effort significantly.
Remove the X-Powered-By header.
How to fix it
- 1Next.js: poweredByHeader: false in next.config.mjs
- 2Express: app.disable("x-powered-by")
- 3PHP: expose_php = Off in php.ini
Code examples
Next.js
// next.config.mjs
export default { poweredByHeader: false };Express
app.disable("x-powered-by");
// Or use helmet: app.use(helmet({ hidePoweredBy: true }));References
Detected automatically by VulnRadar. The check id is x-powered-by-exposed, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is X-Powered-By header reveals application framework?
- VulnRadar rates this low severity in the headers 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 x-powered-by-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-Powered-By header reveals application framework 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.