Cross-site Scripting (XSS) possible due to improper sanitisation of `href` attributes on `<a>` tags (CVE-2024-32463)

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps phlex (rubygems), phlex (rubygems), phlex (rubygems), phlex (rubygems) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
phlexrubygems	>=1.10.0 <1.10.1	1.10.1
phlexrubygems	>=1.9.0 <1.9.2	1.9.2
phlexrubygems	>=1.8.0 <1.8.3	1.8.3
phlexrubygems	>=1.7.0 <1.7.2	1.7.2
phlexrubygems	>=1.6.0 <1.6.3	1.6.3
phlexrubygems	>=1.5.0 <1.5.3	1.5.3
phlexrubygems	>=0 <1.4.2	1.4.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for phlex, phlex, phlex.
Review the reported fix. Update phlex to 1.10.1; phlex to 1.9.2; phlex to 1.8.3; phlex to 1.7.2; phlex to 1.6.3; phlex to 1.5.3; phlex to 1.4.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Apr 17, 2024
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

### Summary There is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data. Our filter to detect and prevent the use of the `javascript:` URL scheme in the `href` attribute of an `<a>` tag could be bypassed with tab `\t` or newline `\n` characters between the characters of the protocol, e.g. `java\tscript:`. ### 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. ```ruby a(href: user_profile) { "Profile" } ``` ### Mitigation The best way to mitigate this vulnerability is to update to one of the following versions: - [1.10.1](https://rubygems.org/gems/phlex/versions/1.10.1) - [1.9.2](https://rubygems.org/gems/phlex/versions/1.9.2) - [1.8.3](https://rubygems.org/gems/phlex/versions/1.8.3) - [1.7.2](https://rubygems.org/gems/phlex/versions/1.7.2) - [1.6.3](https://rubygems.org/gems/phlex/versions/1.6.3) - [1.5.3](https://rubygems.org/gems/phlex/versions/1.5.3) - [1.4.2](https://rubygems.org/gems/phlex/versions/1.4.2) ### Workarounds Configuring a [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) that does not allow [`unsafe-inline`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy#unsafe-inline) would effectively prevent this vulnerability from being exploited.

Quoted source text, attributed separately from HOL analysis.