Silverstripe Form Capture vulnerable to Stored Cross-Site Scripting

published 2023-04-03 3 y ago modified 2026-09-10 1 mo ago also GHSA-38h6-gmr2-j4wx , EUVD-2023-1170

cvss: 6.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits: 0; none known

Silverstripe Form Capture provides a method to capture simple silverstripe forms and an admin interface for users. Starting in version 0.2.0 and prior to versions 1.0.2, 1.1.0, 2.2.5, and 3.1.1, improper escaping when presenting stored form submissions allowed for an attacker to perform a Cross-Site Scripting attack. 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. There are no known workarounds for this vulnerability.

Patch / fix

fixed in 3 links 2

packagist bigfork/silverstripe-form-capture 3.1.1
packagist andrewhaine/silverstripe-form-capture 1.0.2, 2.2.5
bigfork silverstripe_form_capture 2.2.5

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 20 mo ago (2025-02-11)

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
GitHub	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
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 >=2.0.0, <2.2.5 >=1.0.0, <1.0.2	1.0.2 2.2.5

Affected products

bigfork silverstripe-form-capture

Classification

Weakness

CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page
CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary