How severe is GHSA-74j9-xhqr-6qv3?

No CVSS score has been assigned to GHSA-74j9-xhqr-6qv3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-74j9-xhqr-6qv3?

GHSA-74j9-xhqr-6qv3 affects the following packages: silverstripe/framework (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-74j9-xhqr-6qv3?

Update silverstripe/framework to 5.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74j9-xhqr-6qv3 is resolved across your whole dependency graph.

How do I detect GHSA-74j9-xhqr-6qv3 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-74j9-xhqr-6qv3 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-74j9-xhqr-6qv3?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-74j9-xhqr-6qv3 can be triaged on real exposure rather than presence alone.

Is GHSA-74j9-xhqr-6qv3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-74j9-xhqr-6qv3 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-74j9-xhqr-6qv3 published, and has it been updated?

GHSA-74j9-xhqr-6qv3 was published on January 23, 2025 and was last updated on January 23, 2025. 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

GHSA-74j9-xhqr-6qv3 — silverstripe/framework

GHSA-74j9-xhqr-6qv3 is a security vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Reflected Cross Site Scripting (XSS) in error message

Published

Jan 23, 2025

Updated

Jan 23, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jan 23, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘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

If a website has been set to the "dev" environment mode, a URL can be provided which includes an XSS payload which will be executed in the resulting error message.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/framework`	all versions	5.3.8`composer require silverstripe/framework:^5.3.8`

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 5.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74j9-xhqr-6qv3 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-74j9-xhqr-6qv3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-74j9-xhqr-6qv3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

If a website has been set to the "dev" environment mode, a URL can be provided which includes an XSS payload which will be executed in the resulting error message.

O3 Security · Impact-Aware SCA

Is GHSA-74j9-xhqr-6qv3 in your dependencies?

O3 Security finds GHSA-74j9-xhqr-6qv3 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works