CVE-2019-16751: An issue was discovered in Devise Token Auth through 1.1.2

This month

MEDIUM 6.1UPGRADE

CVE-2019-16751 is a medium-severity flaw (CVSS 6.1) affecting devise token auth. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in Devise Token Auth through 1.1.2. The omniauth failure endpoint is vulnerable to Reflected Cross Site Scripting (XSS) through the message parameter. Unauthenticated attackers can craft a URL that executes a malicious JavaScript payload in the victim's browser. This affects the fallback_render method in the omniauth callbacks controller.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-79
Published	2019-09-24
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: devise token auth project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-09-24 18:15 UTCPublished CVE record published
2026-06-17 02:22 UTCUpdated Record last modified

devise token auth project devise token auth UPGRADE

Affected: >= 0.1.33 and <= 1.1.2

Fixed in: newer than 1.1.2

Safe to downgrade to: a release before 0.1.33

1. Check installed version

apt-cache policy devise-token-auth || rpm -q devise-token-auth || devise-token-auth --version

2. UPGRADE to newer than 1.1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade devise-token-auth

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade devise-token-auth

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.1.33 (Debian / Ubuntu)

apt-cache madison devise-token-auth sudo apt install devise-token-auth=<VERSION_BEFORE_0.1.33> sudo apt-mark hold devise-token-auth

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list devise-token-auth sudo dnf downgrade devise-token-auth-<VERSION_BEFORE_0.1.33> sudo dnf versionlock add devise-token-auth

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-16751?

devise token auth: upgrade to newer than 1.1.2. Exact commands for each OS are on this page.

Is CVE-2019-16751 being exploited?

CVE-2019-16751 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-16751 affect?

CVE-2019-16751 affects devise token auth. Severity is medium (CVSS 6.1). An issue was discovered in Devise Token Auth through 1.1.2. The omniauth failure endpoint is vulnerable to Reflected Cross Site Scripting (XSS) through the message parameter. Unauthenticated attackers can craft a URL that executes a malicio

How urgent is CVE-2019-16751?

Priority 41/100. Public exploit reference

References

← Back to latest CVEs