silverstripe/framework ReadOnly transformation for formfields exploitable

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

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Form fields returning isReadonly() as true are vulnerable to reflected XSS injections. This includes ReadonlyField, LookupField, HTMLReadonlyField, as well as special purpose fields like TimeFieldReadonly. Values submitted to through these form fields are not filtered out from the form session data, and might be shown to the user depending on the form behaviour. For example, form validation errors cause the form to re-render with previously submitted values by default. SilverStripe forms automatically load values from request data (GET and POST), which enables malicious use of URLs if your form uses these fields and doesn't overwrite data on form construction. Readonly and disabled form fields are already filtered out in Form-saveInto(), so maliciously submitted data on these fields doesn't make it into the database unless you are accessing form values directly in your saving logic.

Published by the source

23 May 2024, 19:50 UTC

Last modified by the source

23 May 2024, 19:50 UTC

Source last checked

26 Oct 2026, 14:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-97jm-g33h-f46g

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

# Patch Next advisory brief: GHSA-97jm-g33h-f46g

Advisory: silverstripe/framework ReadOnly transformation for formfields exploitable
IDs: GHSA-97jm-g33h-f46g
Record: https://patchnext.com/advisories/ghsa-97jm-g33h-f46g (revision 1, source checked 26 Oct 2026, 14:24 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: silverstripe/framework 3.4.2, 3.3.4, 3.2.6, 3.1.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist silverstripe/framework: affected < 3.1.21; >= 3.2.0, < 3.2.6; >= 3.3.0, < 3.3.4; >= 3.4.0, < 3.4.2; fixed in 3.1.21, 3.4.2, 3.3.4, 3.2.6

## Suggested inspection (read-only)
- Packagist silverstripe/framework: 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 silverstripe/framework.
- 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-97jm-g33h-f46g (GitHub-reviewed advisory GHSA-97jm-g33h-f46g lists affected ranges: Packagist silverstripe/framework >=0 =3.2.0 =3.3.0 =3.4.0 <3.4.2)

Commands are suggestions: review each one before running it.