How severe is GHSA-xc69-p8fc-m6m5?

GHSA-xc69-p8fc-m6m5 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xc69-p8fc-m6m5?

GHSA-xc69-p8fc-m6m5 affects the following packages: silverstripe/subsites (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xc69-p8fc-m6m5?

Update silverstripe/subsites to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xc69-p8fc-m6m5 is resolved across your whole dependency graph.

How do I detect GHSA-xc69-p8fc-m6m5 in my Packagist dependencies?

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

How do I mitigate GHSA-xc69-p8fc-m6m5 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-xc69-p8fc-m6m5?

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

Is GHSA-xc69-p8fc-m6m5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xc69-p8fc-m6m5 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-xc69-p8fc-m6m5 published, and has it been updated?

GHSA-xc69-p8fc-m6m5 was published on May 28, 2024 and was last updated on December 3, 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

HIGH severity

GHSA-xc69-p8fc-m6m5 — silverstripe/subsites

HIGHFix: silverstripe/silverstripe-subsites@bf2c81d

GHSA-xc69-p8fc-m6m5 is a high-severity (CVSS 8.8) vulnerability in silverstripe/subsites. A fix is available for silverstripe/subsites — see the affected versions and patch details below.

silverstripe/subsites Unsafe SQL Query Construction (Safe Data Source)

Published

May 28, 2024

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐘silverstripe/subsites

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

There is a low level potential SQL injection vulnerability in the silverstripe/subsites module has been identified and fixed in version 2.1.1.

Affected Packages

1 total 1 fixed

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

Tailored to GHSA-xc69-p8fc-m6m5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

There is a low level potential SQL injection vulnerability in the silverstripe/subsites module has been identified and fixed in version 2.1.1.

O3 Security · Impact-Aware SCA

Is GHSA-xc69-p8fc-m6m5 in your dependencies?

O3 Security finds GHSA-xc69-p8fc-m6m5 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