Silverstripe Form Capture vulnerable to stored cross-site-scripting

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2023-28851: 0.39% estimated exploitation activity in the next 30 days; percentile 33.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

3 Apr 2023, 21:06 UTC

Last modified by the source

21 Jun 2023, 18:01 UTC

Source last checked

26 Oct 2026, 14:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-38h6-gmr2-j4wx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-28851

Advisory: Silverstripe Form Capture vulnerable to stored cross-site-scripting
IDs: CVE-2023-28851, GHSA-38h6-gmr2-j4wx
Record: https://patchnext.com/advisories/cve-2023-28851 (revision 1, source checked 26 Oct 2026, 14:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: andrewhaine/silverstripe-form-capture 2.2.5, 1.0.2; bigfork/silverstripe-form-capture 3.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist andrewhaine/silverstripe-form-capture: affected >= 2.0.0, < 2.2.5; >= 1.0.0, < 1.0.2; >= 0.2.0, <= 0.2.3; fixed in 1.0.2, 2.2.5
- Packagist bigfork/silverstripe-form-capture: affected >= 3.0.0, < 3.1.1; fixed in 3.1.1

## Suggested inspection (read-only)
- Packagist andrewhaine/silverstripe-form-capture: check the installed version with your package manager.
- Packagist bigfork/silverstripe-form-capture: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on andrewhaine/silverstripe-form-capture, bigfork/silverstripe-form-capture.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-38h6-gmr2-j4wx (GitHub-reviewed advisory GHSA-38h6-gmr2-j4wx lists affected ranges: Packagist bigfork/silverstripe-form-capture >=3.0.0 =2.0.0 =1.0.0 =0.2.0 <=0.2.3)

Commands are suggestions: review each one before running it.