gorilla/csrf is vulnerable to CSRF via form submission from origins that share a top level domain with the target origin.
gorilla/csrf does not validate the Origin header against an allowlist. Its executes its validation of the Referer header for cross-origin requests only when it believes the request is being served over TLS. It determines this by inspecting the r.URL.Scheme
value. However, this value is never populated for "server" requests per the Go spec, and so this check does not run in practice.
// URL specifies either the URI being requested (for server
// requests) or the URL to access (for client requests).
//
// For server requests, the URL is parsed from the URI
// supplied on the Request-Line as stored in RequestURI. For
// most requests, fields other than Path and RawQuery will be
// empty. (See [RFC 7230, Section 5.3](https://rfc-editor.org/rfc/rfc7230.html#section-5.3))
//
// For client requests, the URL's Host specifies the server to
// connect to, while the Request's Host field optionally
// specifies the Host header value to send in the HTTP
// request.
URL *[url](https://pkg.go.dev/net/url).[URL](https://pkg.go.dev/net/url#URL)
target.example.test
protected with gorilla/csrf and served over TLS hosting form on /submit
attack.example.test
served over TLStarget.example.test
domain=.example.test and path=/submit
/
(the default for CSRF cookies) it will be sent first by the browser on submit to our target originattack.example.test
with exfiltrated CSRF form tokenattack.example.test
Origin / Referer headers are not validated. This vulnerability allows an attacker who has gained XSS on a subdomain or top level domain to perform authenticated form submissions against gorilla/csrf protected targets that share the same top level domain.
This bug has existed in gorilla/csrf since its initial release in 2015.
{ "nvd_published_at": "2025-04-15T19:16:07Z", "cwe_ids": [ "CWE-352" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2025-04-14T15:26:07Z" }