How severe is GHSA-38h6-gmr2-j4wx?

GHSA-38h6-gmr2-j4wx has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-38h6-gmr2-j4wx?

GHSA-38h6-gmr2-j4wx affects the following packages: bigfork/silverstripe-form-capture (Packagist), andrewhaine/silverstripe-form-capture (Packagist), andrewhaine/silverstripe-form-capture (Packagist), andrewhaine/silverstripe-form-capture (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-38h6-gmr2-j4wx?

Update bigfork/silverstripe-form-capture to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-38h6-gmr2-j4wx is resolved across your whole dependency graph.

How do I detect GHSA-38h6-gmr2-j4wx in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bigfork/silverstripe-form-capture. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-38h6-gmr2-j4wx 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-38h6-gmr2-j4wx?

O3 pinpoints whether GHSA-38h6-gmr2-j4wx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-38h6-gmr2-j4wx actively exploited in the wild?

No public exploit code has been indexed for GHSA-38h6-gmr2-j4wx 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.

What is the EPSS score for GHSA-38h6-gmr2-j4wx?

GHSA-38h6-gmr2-j4wx has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-38h6-gmr2-j4wx published, and has it been updated?

GHSA-38h6-gmr2-j4wx was published on April 3, 2023 and was last updated on February 16, 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

GHSA-38h6-gmr2-j4wx

MEDIUM

Silverstripe Form Capture vulnerable to stored cross-site-scripting

Also known asCVE-2023-28851

Published

Apr 3, 2023

Updated

Feb 16, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk31th percentile-0.15%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

🐘bigfork/silverstripe-form-capture🐘andrewhaine/silverstripe-form-capture🐘andrewhaine/silverstripe-form-capture🐘andrewhaine/silverstripe-form-capture

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

Impact

Improper escaping when presenting stored form submissions allowed for an attacker to perform a Cross-Site Scripting attack

Patches

The vulnerability was initially patched in version 1.0.2, and version 1.1.0 includes this patch. The bug was then accidentally re-introduced during a merge error, and has been re-patched in versions 2.2.5 and 3.1.1.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`bigfork/silverstripe-form-capture`	≥ 3.0.0&&< 3.1.1	3.1.1
🐘Packagist	`andrewhaine/silverstripe-form-capture`	≥ 0.2.0&&< 1.0.2	1.0.2
🐘Packagist	`andrewhaine/silverstripe-form-capture`	≥ 2.0.0&&< 2.2.5	2.2.5
🐘Packagist	`andrewhaine/silverstripe-form-capture`	≥ 1.0.0&&< 1.0.2	1.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bigfork/silverstripe-form-capture. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update bigfork/silverstripe-form-capture to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-38h6-gmr2-j4wx 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 pinpoints whether GHSA-38h6-gmr2-j4wx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-38h6-gmr2-j4wx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Improper escaping when presenting stored form submissions allowed for an attacker to perform a Cross-Site Scripting attack ### Patches The vulnerability was initially patched in version 1.0.2, and version 1.1.0 includes this patch. The bug was then accidentally re-introduced during a merge error, and has been re-patched in versions 2.2.5 and 3.1.1.

O3 Security · Impact-Aware SCA

Is GHSA-38h6-gmr2-j4wx in your dependencies?

O3 detects GHSA-38h6-gmr2-j4wx across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works