phlex
Affected
- introduced
2.4.0.beta1, fixed2.4.1(ecosystem)
Fixed versions
2.4.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: None
Phlex XSS protection bypass via attribute splatting, dynamic tags, and href values
Impact
During a security audit conducted with Claude Opus 4.6 and GPT-5.3-Codex, we identified three specific ways to bypass the XSS (cross-site-scripting) protection built into Phlex.
div(**user_attributes).tag method, e.g. tag(some_tag_name_from_user).href attributes, e.g. a(href: user_provided_link).All three of these patterns are meant to be safe and all have now been patched.
Patches
Phlex has patched all three issues and introduced new tests that run against Safari, Firefox and Chrome.
The patched versions are:
Phlex has also patched the `main` branch in GitHub.
Workarounds
If a project uses a secure CSP (content security policy) or if the application doesn’t use any of the above patterns, it is not at risk.
High Basis: The source's own band: HIGH
2.4.0.beta1, fixed 2.4.1 (ecosystem)2.4.1
The export has no generic command for this ecosystem.
2.3.0, fixed 2.3.2 (ecosystem)2.3.2
The export has no generic command for this ecosystem.
2.2.0, fixed 2.2.2 (ecosystem)2.2.2
The export has no generic command for this ecosystem.
2.1.0, fixed 2.1.3 (ecosystem)2.1.3
The export has no generic command for this ecosystem.
2.0.0.beta1, fixed 2.0.2 (ecosystem)2.0.2
The export has no generic command for this ecosystem.
0, fixed 1.11.1 (ecosystem)1.11.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0