Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-38h6-gmr2-j4wx: Silverstripe Form Capture vulnerable to stored cross-site-scripting

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.

ghsa
#xss#vulnerability#git

Package

composer andrewhaine/silverstripe-form-capture (Composer)

Affected versions

>= 0.2.0, <= 0.2.3

>= 2.0.0, <= 2.2.4

>= 1.0.0, <= 1.0.1

Patched versions

1.0.2

2.2.5

1.1.0

composer bigfork/silverstripe-form-capture (Composer)

>= 3.0.0, <= 3.1.0

3.1.1

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.

References

  • GHSA-38h6-gmr2-j4wx
  • https://nvd.nist.gov/vuln/detail/CVE-2023-28851
  • bigfork/silverstripe-form-capture@5b3aa39

kinglozzer published to bigfork/silverstripe-form-capture

Apr 3, 2023

Published by the National Vulnerability Database

Apr 3, 2023

Published to the GitHub Advisory Database

Apr 3, 2023

Reviewed

Apr 3, 2023

Related news

CVE-2023-28851: Improper Handling of User Input - Cross-Site Scripting (Stored)

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.