Skip to main content
LowHeadersOWASP A05:2021CWE-200

How to fix: X-AspNetMvc-Version header exposes MVC version

The X-AspNetMvc-Version header reveals which version of ASP.NET MVC the application is running.

Why it matters

The specific MVC version helps attackers identify framework-specific vulnerabilities and apply targeted exploits.

Disable the header in your MvcHandler configuration.

How to fix it

  1. 1In Global.asax Application_Start: MvcHandler.DisableMvcResponseHeader = true;

Code examples

Global.asax.cs

C#
protected void Application_Start() {
  MvcHandler.DisableMvcResponseHeader = true;
}

References

Detected automatically by VulnRadar. The check id is x-aspnetmvc-version-exposed, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is X-AspNetMvc-Version header exposes MVC version?
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-aspnetmvc-version-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does X-AspNetMvc-Version header exposes MVC version 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.

Propose a checkHow a check is built

Scan your own site for x-aspnetmvc-version header exposes mvc version

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

X-AspNetMvc-Version header exposes MVC version | VulnRadar