CVE intelligence and bounded remediation

CVE-2023-28851 — Silverstripe Form Capture provides a method to capture simple silverstripe forms and an admin interface for users

Medium CVSS 6.1

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.

Severity
Medium
CVSS
6.1 (3.1)
Published
2023-04-03
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-79, CWE-80

Affected products

  • bigfork / silverstripe_form_capture
  • bigfork / silverstripe_form_capture / 1.0
  • bigfork / silverstripe_form_capture / 1.0.1
  • bigfork / silverstripe_form_capture / 3.0.0
  • bigfork / silverstripe_form_capture / 3.1.0

Showing 5 representative product identities from 6 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Cross-site scripting and unsafe browser output

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
  • Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
  • Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.

Remediate safely

  • Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
  • Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
  • Update affected rendering components and add tests for every output context using inert sentinel markup.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.