Skip to main content
InfoSSLOWASP A01:2021CWE-284

How to fix: X-HTTP-Method-Override / X-Forwarded-Method Header in Response

The response includes a header literally named X-HTTP-Method-Override or X-Forwarded-Method. These are conventionally request headers a client sends to ask the server to treat a request as a different HTTP verb, not headers a server sends back, so seeing one in a response is unusual and worth a look.

Why it matters

This is a passive observation, not proof of a bypass: the scanner did not send an override header and compare behavior, it only saw the header name in the response. A common cause is debugging/tracing middleware or a reverse proxy echoing inbound header names back for observability.

If your application does honor a client-supplied X-HTTP-Method-Override or X-Forwarded-Method to change the effective HTTP method, that is a real method-spoofing risk worth checking separately with an active test (send an override header and compare the resulting behavior against a plain request of that verb).

How to fix it

  1. 1Confirm whether your application or reverse proxy actually acts on these headers; if not, this is informational only.
  2. 2If it does honor them, configure the reverse proxy to strip X-Forwarded-Method and X-HTTP-Method-Override from inbound client requests, and enforce method-based authorization at the origin using the wire-level method.
  3. 3Stop echoing inbound header names back in responses unless needed for debugging.

Code examples

Nginx: strip override headers

nginx
proxy_set_header X-HTTP-Method-Override '';
proxy_set_header X-Forwarded-Method '';
proxy_set_header X-Method-Override '';

References

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

See every ssl check

Questions

How severe is X-HTTP-Method-Override / X-Forwarded-Method Header in Response?
VulnRadar rates this info severity in the ssl 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-forwarded-method-override, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does X-HTTP-Method-Override / X-Forwarded-Method Header in Response map to?
It maps to CWE-284. In the OWASP Top 10 it falls under A01: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-http-method-override / x-forwarded-method header in response

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-HTTP-Method-Override / X-Forwarded-Method Header in Response | VulnRadar