How severe is GHSA-w8fq-xgvh-cxc2?

GHSA-w8fq-xgvh-cxc2 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-w8fq-xgvh-cxc2?

GHSA-w8fq-xgvh-cxc2 affects the following packages: silverstripe/forum (Packagist), silverstripe/forum (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-w8fq-xgvh-cxc2?

Update silverstripe/forum to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w8fq-xgvh-cxc2 is resolved across your whole dependency graph.

How do I detect GHSA-w8fq-xgvh-cxc2 in my Packagist dependencies?

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

How do I mitigate GHSA-w8fq-xgvh-cxc2 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-w8fq-xgvh-cxc2?

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

Is GHSA-w8fq-xgvh-cxc2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w8fq-xgvh-cxc2 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-w8fq-xgvh-cxc2 published, and has it been updated?

GHSA-w8fq-xgvh-cxc2 was published on May 23, 2024 and was last updated on November 28, 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

MEDIUM severity

GHSA-w8fq-xgvh-cxc2 — silverstripe/forum

MEDIUMFix: silverstripe-archive/silverstripe-forum@0ec7c92

GHSA-w8fq-xgvh-cxc2 is a medium-severity (CVSS 5.3) vulnerability in silverstripe/forum. A fix is available for silverstripe/forum — see the affected versions and patch details below.

Silverstripe Forum Module CSRF Vulnerability

Published

May 23, 2024

Updated

Nov 28, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘silverstripe/forum🐘silverstripe/forum

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

A number of form actions in the Forum module are directly accessible. A malicious user (e.g. spammer) can use GET requests to create Members and post to forums, bypassing CSRF and anti-spam measures.

Additionally, a forum moderator could be tricked into clicking a specially crafted URL, resulting in a topic being moved.

Thanks to Michael Strong for discovering.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/forum`	all versions	0.6.2`composer require silverstripe/forum:^0.6.2`
🐘Packagist	`silverstripe/forum`	≥ 0.7.0&&< 0.7.4	0.7.4`composer require silverstripe/forum:^0.7.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/forum, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/forum to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w8fq-xgvh-cxc2 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-w8fq-xgvh-cxc2 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

A number of form actions in the Forum module are directly accessible. A malicious user (e.g. spammer) can use GET requests to create Members and post to forums, bypassing CSRF and anti-spam measures. Additionally, a forum moderator could be tricked into clicking a specially crafted URL, resulting in a topic being moved. Thanks to Michael Strong for discovering.

O3 Security · Impact-Aware SCA

Is GHSA-w8fq-xgvh-cxc2 in your dependencies?

O3 Security finds GHSA-w8fq-xgvh-cxc2 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