How severe is GHSA-c4c3-j73v-634r?

No CVSS score has been assigned to GHSA-c4c3-j73v-634r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c4c3-j73v-634r?

GHSA-c4c3-j73v-634r affects the following packages: silverstripe/framework (Packagist), silverstripe/framework (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-c4c3-j73v-634r?

Update silverstripe/framework to 3.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c4c3-j73v-634r is resolved across your whole dependency graph.

How do I detect GHSA-c4c3-j73v-634r in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c4c3-j73v-634r 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.

Is GHSA-c4c3-j73v-634r actively exploited in the wild?

No public exploit code has been indexed for GHSA-c4c3-j73v-634r 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-c4c3-j73v-634r published, and has it been updated?

GHSA-c4c3-j73v-634r 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

Not in CISA KEV

silverstripe/framework has Cross-site Scripting vulnerability in page history comparisonGHSA-c4c3-j73v-634r

Fix: silverstripe/silverstripe-framework@2b72c0f

GHSA-c4c3-j73v-634r is a security vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Published

May 27, 2024

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘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

Authenticated user with page edit permission can craft HTML, which when rendered in a page history comparison can execute client scripts.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/framework`	≥ 3.4.0-rc1&&< 3.4.6	3.4.6`composer require silverstripe/framework:^3.4.6`
🐘Packagist	`silverstripe/framework`	≥ 3.5.0-rc1&&< 3.5.4	3.5.4`composer require silverstripe/framework:^3.5.4`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/framework to 3.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c4c3-j73v-634r 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.

Frequently Asked Questions

Authenticated user with page edit permission can craft HTML, which when rendered in a page history comparison can execute client scripts.

O3 Security · Impact-Aware SCA

Is GHSA-c4c3-j73v-634r in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works