CVE-2024-32970

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 48% 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
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.1Exploit: NoneExposed: 0

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

Phlex is a framework for building object-oriented views in Ruby. In affected versions there is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data. Since the last two vulnerabilities https://github.com/phlex-ruby/phlex/security/advisories/GHSA-242p-4v39-2v8g and https://github.com/phlex-ruby/phlex/security/advisories/GHSA-g7xq-xv8c-h98c, we have invested in extensive browser tests. It was these new tests that helped us uncover these issues. As of now the project exercises every possible attack vector the developers can think of — including enumerating every ASCII character, and we run these tests in Chrome, Firefox and Safari. Additionally, we test against a list of 6613 known XSS payloads (see: payloadbox/xss-payload-list). The reason these issues were not detected before is the escapes were working as designed. However, their design didn't take into account just how recklessly permissive browsers are when it comes to executing unsafe JavaScript via HTML attributes. If you render an ` tag with an href attribute set to a user-provided link, that link could potentially execute JavaScript when clicked by another user. If you splat user-provided attributes when rendering any HTML or SVG tag, malicious event attributes could be included in the output, executing JavaScript when the events are triggered by another user. Patches are available on RubyGems for all minor versions released in the last year. Users are advised to upgrade. Users unable to upgrade should configure a Content Security Policy that does not allow unsafe-inline which would effectively prevent this vulnerability from being exploited. Users who upgrade are also advised to configure a Content Security Policy header that does not allow unsafe-inline`.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
49.3%
KEV
Not listed

Published

April 30, 2024

Last Modified

April 15, 2026

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
phlex1.10.0, 1.10.11.10.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 52× 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.

Showing the most recent 100 of 111 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-32970?
CVE-2024-32970 is a high vulnerability published on April 30, 2024. Phlex is a framework for building object-oriented views in Ruby. In affected versions there is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data. Since the last two vulnerabilities…
When was CVE-2024-32970 disclosed?
CVE-2024-32970 was first published in the National Vulnerability Database on April 30, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-32970 actively exploited?
CVE-2024-32970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 49.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-32970?
CVE-2024-32970 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-32970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-32970, 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-2024-32970

Explore →

Is Your Infrastructure Affected by CVE-2024-32970?

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