CVE-2019-16751 — Vulnerability in devise_token_auth — CVE Details
Devise Token Auth vulnerable to Cross-site Scripting
Summary
Advisory Timeline
- First published May 24, 2022 (1602 days ago).
- Last revised February 16, 2024 — 633 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
gem install devise_token_auth -v 1.1.3
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: rubygems (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| devise_token_auth | rubygems | 0.1.33, 0.1.34, 0.1.35, 0.1.36 (+19 more) | 1.1.3 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-79Cross-site Scripting (XSS)MITRE
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 6.1 score means for each attack dimension.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
References
Frequently Asked Questions
- What is CVE-2019-16751?
- Devise Token Auth vulnerable to Cross-site Scripting This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 6.1/10).
- How do I check if my project is affected by CVE-2019-16751?
- CVE-2019-16751 affects devise_token_auth. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2019-16751 and 200,000+ other known vulnerabilities.
Severity & Exploitability
Exploitation requires specific conditions or has limited impact. Remediate within weeks.
Also Known As
Related CVEs
- CVE-2026-107715MEDIUM
Mechanize sends credential headers to another host after an HTTP redirect
- CVE-2026-107399MEDIUM
Mechanize sends credential headers to another origin after a meta refresh
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies