Skip to content
Fencer Vulns
high 7.3

CVE-2025-47909 json

Improper validation of TrustedOrigins allows CSRF attacks in github.com/gorilla/csrf

published 2025-08-29 14 mo ago modified 2026-10-19 20 d ago also GHSA-82ff-hg59-8x73 , GO-2025-3884 , EUVD-2025-26212

cvss
7.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

Hosts listed in TrustedOrigins implicitly allow requests from the corresponding HTTP origins, allowing network MitMs to perform CSRF attacks. After the CVE-2025-24358 fix, a network attacker that places a form at http://example.com can't get it to submit to https://example.com because the Origin header is checked with sameOrigin against a synthetic URL. However, if a host is added to TrustedOrigins, both its HTTP and HTTPS origins will be allowed, because the schema of the synthetic URL is ignored and only the host is checked. For example, if an application is hosted on https://example.com and adds example.net to TrustedOrigins, a network attacker can serve a form at http://example.net to perform the attack. Applications should migrate to net/http.CrossOriginProtection, introduced in Go 1.25. If that is not an option, a backport is available as a module at filippo.io/csrf, and a drop-in replacement for the github.com/gorilla/csrf API is available at filippo.io/csrf/gorilla.

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
14 mo ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CNA 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/gorilla/csrf
<=1.7.3
>=1.7.3
 no fix listed

Affected products

  • github.com/gorilla/csrf github.com/gorilla/csrf

Classification

Weakness
  • CWE-346 Origin Validation Error
  • CWE-352 Cross-Site Request Forgery
  • CWE-807 Reliance on Untrusted Inputs in a Security Decision

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.