Phlex vulnerable to Cross-site Scripting (XSS) via maliciously formed HTML attribute names and values
Published 1 May 2024 · Updated 10 Sept 2026
Is your project on an affected phlex?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <1.9.3
- Fixed in
- 1.9.3
bundle update --conservative phlex # Gemfile: '>= 1.9.3'- Affected
- >=1.10.0 <1.10.2
- Fixed in
- 1.10.2
bundle update --conservative phlex # Gemfile: '>= 1.10.2'Details
There is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data.
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 browser are when it comes to executing unsafe JavaScript via HTML attributes.
Impact
If you render an <a> tag with an href attribute set to a user-provided link, that link could potentially execute JavaScript when clicked by another user.
a(href: user_profile) { "Profile" }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.
h1(**JSON.parse(user_attributes))
Patches
Patches are available on RubyGems for all minor versions released in the last year.
If you are on main, it has been patched since `da8f943`
Workarounds
Configuring a Content Security Policy that does not allow `unsafe-inline` would effectively prevent this vulnerability from being exploited.
References
In addition to upgrading to a patched version of Phlex, we strongly recommend configuring a Content Security Policy header that does not allow unsafe-inline. Here’s how you can configure a Content Security Policy header in Rails. https://guides.rubyonrails.org/security.html#content-security-policy-header
Is GHSA-9p57-h987-4vgx in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected phlex, and gives you the command that fixes it.
More advisories for phlex
- HighGHSA-w67g-2h6v-vjgqPhlex XSS protection bypass via attribute splatting, dynamic tags, and href values · 6 Feb 2026
- HighCVE-2024-32463Cross-site Scripting (XSS) possible due to improper sanitisation of `href` attributes on `<a>` tags · 17 Apr 2024
- HighCVE-2024-28199Cross-site Scripting (XSS) possible with maliciously formed HTML attribute names and values in Phlex · 12 Mar 2024
References
- Linkgithub.com/phlex-ruby/phlex/security/advisories/GHSA-9p57-h987-4vgx
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-32970
- Linkgithub.com/phlex-ruby/phlex/commit/da8f94342a84cff9d78c98bcc3b3604ee2e577d2
- Linkdeveloper.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
- Linkdeveloper.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy#unsafe-inline
- Linkgithub.com/payloadbox/xss-payload-list
- Packagegithub.com/phlex-ruby/phlex
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/phlex/CVE-2024-32970.yml
- Linkrubygems.org/gems/phlex
- Linkrubygems.org/gems/phlex/versions/1.10.2
- Linkrubygems.org/gems/phlex/versions/1.9.3
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.