How severe is GHSA-f43j-8hq4-2xj9?

No CVSS score has been assigned to GHSA-f43j-8hq4-2xj9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f43j-8hq4-2xj9?

GHSA-f43j-8hq4-2xj9 affects the following packages: silverstripe/framework (Packagist), silverstripe/framework (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-f43j-8hq4-2xj9?

Update silverstripe/framework to 4.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f43j-8hq4-2xj9 is resolved across your whole dependency graph.

How do I detect GHSA-f43j-8hq4-2xj9 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-f43j-8hq4-2xj9 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-f43j-8hq4-2xj9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f43j-8hq4-2xj9 can be triaged on real exposure rather than presence alone.

Is GHSA-f43j-8hq4-2xj9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f43j-8hq4-2xj9 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-f43j-8hq4-2xj9 published, and has it been updated?

GHSA-f43j-8hq4-2xj9 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

GHSA-f43j-8hq4-2xj9 — silverstripe/framework

Fix: silverstripe/silverstripe-framework@5b7eca2

GHSA-f43j-8hq4-2xj9 is a security vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

silverstripe/framework uploaded PHP script execution in assets

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

In addition, sites hosted on the New Zealand Common Web Platform or SilverStripe Platform have additional configuration in place which prevents PHP script execution in assets, even in a malicious party manages to upload these into the folder.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/framework`	≥ 4.0.0-rc1&&< 4.0.4	4.0.4`composer require silverstripe/framework:^4.0.4`
🐘Packagist	`silverstripe/framework`	≥ 4.1.0-rc1&&< 4.1.1	4.1.1`composer require silverstripe/framework:^4.1.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/framework to 4.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f43j-8hq4-2xj9 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-f43j-8hq4-2xj9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f43j-8hq4-2xj9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A weakness in the .htaccess rules preventing requests to uploaded PHP scripts allows PHP scripts that had made their way into the assets directory to be successfully executed through the use of a specially crafted URL. There are protections in place to disallow upload of PHP scripts through the CMS, meaning this weakness does not lead to direct vulnerabilities. In addition, sites hosted on the New Zealand Common Web Platform or SilverStripe Platform have additional configuration in place which prevents PHP script execution in assets, even in a malicious party manages to upload these into the

O3 Security · Impact-Aware SCA

Is GHSA-f43j-8hq4-2xj9 in your dependencies?

O3 Security finds GHSA-f43j-8hq4-2xj9 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