How severe is GHSA-468j-6jrc-2rjx?

GHSA-468j-6jrc-2rjx has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-468j-6jrc-2rjx?

GHSA-468j-6jrc-2rjx affects the following packages: silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist), silverstripe/framework (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-468j-6jrc-2rjx?

Update silverstripe/framework to 3.1.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-468j-6jrc-2rjx is resolved across your whole dependency graph.

How do I detect GHSA-468j-6jrc-2rjx in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-468j-6jrc-2rjx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-468j-6jrc-2rjx?

O3 pinpoints whether GHSA-468j-6jrc-2rjx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-468j-6jrc-2rjx actively exploited in the wild?

No public exploit code has been indexed for GHSA-468j-6jrc-2rjx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-468j-6jrc-2rjx published, and has it been updated?

GHSA-468j-6jrc-2rjx was published on May 27, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-468j-6jrc-2rjx

MEDIUM

silverstripe/framework vulnerable to Cross-site Scripting In `OptionsetField` and `CheckboxSetField`

Published

May 27, 2024

Updated

Dec 2, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

List of key / value pairs assigned to OptionsetField or CheckboxSetField do not have a default casting assigned to them. The effect of this is a potential XSS vulnerability in lists where either key or value contain unescaped HTML.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/framework`	≥ 3.1.19-rc1&&< 3.1.20	3.1.20
🐘Packagist	`silverstripe/framework`	≥ 3.2.4-rc1&&< 3.2.5	3.2.5
🐘Packagist	`silverstripe/framework`	≥ 3.3.2-rc1&&< 3.3.3	3.3.3
🐘Packagist	`silverstripe/framework`	≥ 3.4.0-rc1&&< 3.4.1	3.4.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update silverstripe/framework to 3.1.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-468j-6jrc-2rjx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-468j-6jrc-2rjx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-468j-6jrc-2rjx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

List of key / value pairs assigned to `OptionsetField` or `CheckboxSetField` do not have a default casting assigned to them. The effect of this is a potential XSS vulnerability in lists where either key or value contain unescaped HTML.

O3 Security · Impact-Aware SCA

Is GHSA-468j-6jrc-2rjx in your dependencies?

O3 detects GHSA-468j-6jrc-2rjx across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works