CVE-2021-28680

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The devise_masquerade gem before 1.3 allows certain attacks when a password's salt is unknown. An application that uses this gem to let administrators masquerade/impersonate users loses one layer of security protection compared to a situation where Devise (without this extension) is used. If the server-side secret_key_base value became publicly known (for instance if it is committed to a public repository by mistake), there are still other protections in place that prevent an attacker from impersonating any user on the site. When masquerading is not used in a plain Devise application, one must know the password salt of the target user if one wants to encrypt and sign a valid session cookie. When devise_masquerade is used, however, an attacker can decide which user the "back" action will go back to without knowing that user's password salt and simply knowing the user ID, by manipulating the session cookie and pretending that a user is already masqueraded by an administrator.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
65.0%
KEV
Not listed

Published

December 7, 2021

Last Modified

November 21, 2024

References (4)

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
devise_masquerade0.0.1 ... 1.3.0 (36 versions)1.3.1—

Data Freshness Timeline

(refreshed 10× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:00 UTCEPSS rescore
  2. 2026-07-15 16:55 UTCEPSS rescore
  3. 2026-07-15 16:55 UTCEPSS rescore
  4. 2026-07-15 01:58 UTCEPSS rescore
  5. 2026-07-13 22:27 UTCEPSS rescore
  6. 2026-07-13 22:27 UTCEPSS rescore
  7. 2026-07-12 05:44 UTCEPSS rescore
  8. 2026-07-12 05:44 UTCEPSS rescore
  9. 2026-07-11 08:25 UTCEPSS rescore
  10. 2026-07-11 08:25 UTCEPSS rescore
  11. 2026-07-09 19:07 UTCEPSS rescore
  12. 2026-07-08 15:12 UTCEPSS rescore
  13. 2026-07-07 13:43 UTCEPSS rescore
  14. 2026-07-06 16:25 UTCEPSS rescore
  15. 2026-07-06 16:25 UTCEPSS rescore
  16. 2026-07-06 02:21 UTCEPSS rescore
  17. 2026-07-06 02:21 UTCEPSS rescore
  18. 2026-07-05 02:28 UTCEPSS rescore
  19. 2026-07-04 06:29 UTCEPSS rescore
  20. 2026-07-04 06:29 UTCEPSS rescore
  21. 2026-07-02 16:57 UTCEPSS rescore
  22. 2026-07-01 15:03 UTCEPSS rescore
  23. 2026-06-30 23:20 UTCEPSS rescore
  24. 2026-06-30 23:20 UTCEPSS rescore
  25. 2026-06-30 03:30 UTCOSV refresh
Show 62 more
  1. 2026-06-29 14:04 UTCEPSS rescore
  2. 2026-06-28 14:05 UTCEPSS rescore
  3. 2026-06-28 04:54 UTCEPSS rescore
  4. 2026-06-28 04:54 UTCEPSS rescore
  5. 2026-06-27 03:06 UTCEPSS rescore
  6. 2026-06-27 03:06 UTCEPSS rescore
  7. 2026-06-25 13:48 UTCEPSS rescore
  8. 2026-06-25 13:48 UTCEPSS rescore
  9. 2026-06-24 14:03 UTCEPSS rescore
  10. 2026-06-24 14:03 UTCEPSS rescore
  11. 2026-06-23 21:31 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-22 14:24 UTCEPSS rescore
  14. 2026-06-22 14:24 UTCEPSS rescore
  15. 2026-06-21 14:55 UTCEPSS rescore
  16. 2026-06-21 14:54 UTCEPSS rescore
  17. 2026-06-21 01:58 UTCEPSS rescore
  18. 2026-06-21 01:58 UTCEPSS rescore
  19. 2026-06-19 19:24 UTCEPSS rescore
  20. 2026-06-19 19:24 UTCEPSS rescore
  21. 2026-06-18 17:51 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-17 17:51 UTCEPSS rescore
  24. 2026-06-16 17:51 UTCEPSS rescore
  25. 2026-06-15 17:46 UTCEPSS rescore
  26. 2026-06-14 23:15 UTCEPSS rescore
  27. 2026-06-13 22:58 UTCEPSS rescore
  28. 2026-06-13 22:58 UTCEPSS rescore
  29. 2026-06-12 23:10 UTCEPSS rescore
  30. 2026-06-12 15:40 UTCOSV refresh
  31. 2026-06-11 13:58 UTCEPSS rescore
  32. 2026-06-10 22:16 UTCEPSS rescore
  33. 2026-06-10 13:20 UTCEPSS rescore
  34. 2026-06-08 14:15 UTCEPSS rescore
  35. 2026-06-07 15:23 UTCEPSS rescore
  36. 2026-06-07 15:23 UTCEPSS rescore
  37. 2026-06-06 13:46 UTCEPSS rescore
  38. 2026-06-06 13:46 UTCEPSS rescore
  39. 2026-06-06 13:46 UTCEPSS rescore
  40. 2026-06-05 22:45 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 06:09 UTCEPSS rescore
  43. 2026-06-05 06:09 UTCEPSS rescore
  44. 2026-06-04 13:10 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-02 20:11 UTCEPSS rescore
  47. 2026-06-02 20:11 UTCEPSS rescore
  48. 2026-06-02 20:11 UTCEPSS rescore
  49. 2026-06-01 13:50 UTCEPSS rescore
  50. 2026-06-01 13:50 UTCEPSS rescore
  51. 2026-05-31 22:29 UTCEPSS rescore
  52. 2026-05-31 22:29 UTCEPSS rescore
  53. 2026-05-31 00:15 UTCEPSS rescore
  54. 2026-05-29 13:42 UTCEPSS rescore
  55. 2026-05-28 13:43 UTCEPSS rescore
  56. 2026-05-28 13:43 UTCEPSS rescore
  57. 2026-05-27 13:39 UTCEPSS rescore
  58. 2026-05-27 13:39 UTCEPSS rescore
  59. 2026-05-26 13:42 UTCEPSS rescore
  60. 2026-05-26 07:17 UTCEPSS rescore
  61. 2026-05-26 07:17 UTCEPSS rescore
  62. 2026-05-26 06:47 UTCEG score recompute

Frequently asked(5)

What is CVE-2021-28680?
CVE-2021-28680 is a high vulnerability published on December 7, 2021. The devisemasquerade gem before 1.3 allows certain attacks when a password's salt is unknown. An application that uses this gem to let administrators masquerade/impersonate users loses one layer of security protection compared to a situation where Devise (without this extension) is used. If the…
When was CVE-2021-28680 disclosed?
CVE-2021-28680 was first published in the National Vulnerability Database on December 7, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-28680 actively exploited?
CVE-2021-28680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 65.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-28680?
CVE-2021-28680 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2021-28680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-28680, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-28680

Explore →

Is Your Infrastructure Affected by CVE-2021-28680?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs