CVE-2020-8167Network attack vector

CSRF token disclosure via cross-domain XHR

Published Jun 19, 2020 · Updated Aug 4, 2024

Cross-site request forgery in Ruby on Rails rails-ujs before 5.2.4.3 and 6.0.0 through 6.0.3 allows remote attackers to disclose CSRF tokens. The createXHR routine adds X-CSRF-Token to XMLHttpRequest objects without first excluding cross-domain requests, so a crafted cross-origin form action or link target receives the token. The application must use rails-ujs, expose attacker control over a POST-triggering href or form action, and persuade a user to activate it; the bounded consequence is disclosure of that user's CSRF token to the attacker's domain.

CVSS severity6.5
Medium
EPSS probability1.49%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cross-site request forgery in Ruby on Rails rails-ujs before 5.2.4.3 and 6.0.0 through 6.0.3 allows remote attackers to disclose CSRF tokens. The createXHR routine adds X-CSRF-Token to XMLHttpRequest objects without first excluding cross-domain requests, so a crafted cross-origin form action or link target receives the token. The application must use rails-ujs, expose attacker control over a POST-triggering href or form action, and persuade a user to activate it; the bounded consequence is disclosure of that user's CSRF token to the attacker's domain.

The record

CVE
CVE-2020-8167
Published
Jun 19, 2020
Updated
Aug 4, 2024
Vendor
Ruby on Rails
Product
Ruby on Rails
Classifications
CWE-352, T1189
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 19, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Fixed in 5.2.4.3, 6.0.3.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Ruby on Rails · Ruby on Railsversion=Fixed in 5.2.4.3, 6.0.3.1

Published CVSS scores

6.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
4.3NIST NVDAV:N/AC:M/Au:N/C:N/I:P/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)
T1189Drive-by Compromise

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo