How severe is GHSA-frm9-7pm9-5rgc?

GHSA-frm9-7pm9-5rgc has a CVSS score of 4.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-frm9-7pm9-5rgc?

GHSA-frm9-7pm9-5rgc affects the following packages: silverstripe/comments (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-frm9-7pm9-5rgc?

Update silverstripe/comments to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-frm9-7pm9-5rgc is resolved across your whole dependency graph.

How do I detect GHSA-frm9-7pm9-5rgc in my Packagist dependencies?

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

How do I mitigate GHSA-frm9-7pm9-5rgc 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-frm9-7pm9-5rgc?

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

Is GHSA-frm9-7pm9-5rgc actively exploited in the wild?

No public exploit code has been indexed for GHSA-frm9-7pm9-5rgc 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-frm9-7pm9-5rgc published, and has it been updated?

GHSA-frm9-7pm9-5rgc 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

MEDIUM severity

GHSA-frm9-7pm9-5rgc — silverstripe/comments

MEDIUM

GHSA-frm9-7pm9-5rgc is a medium-severity (CVSS 4.4) vulnerability in silverstripe/comments. A fix is available for silverstripe/comments — see the affected versions and patch details below.

SilverStripe comments module includes version of jQuery vulnerable to Cross-site Scripting

Published

May 27, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐘silverstripe/comments

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

CWP 2.0.0 has been released with the fixed cwp/stater-theme and silverstripe/comments module, and SilverStripe 4.2.0 will be released with the fixed silverstripe-themes/simple theme.

Affected Packages

1 total 1 fixed

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

Tailored to GHSA-frm9-7pm9-5rgc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The silverstripe/comments module, the cwp/starter-theme and the cwp/watea-theme include an outdated version of jQuery by default, which contains XSS vulnerabilities if user input is used in certain contexts. Though no known exploit has been found for these in the existing usage, user customisation to these themes could have made them exploitable. CWP 2.0.0 has been released with the fixed cwp/stater-theme and silverstripe/comments module, and SilverStripe 4.2.0 will be released with the fixed silverstripe-themes/simple theme.

O3 Security · Impact-Aware SCA

Is GHSA-frm9-7pm9-5rgc in your dependencies?

O3 Security finds GHSA-frm9-7pm9-5rgc 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