MediumGHSA-r9vp-fp72-xgf7

silverstripe/framework's `Member.Name` is not escaped

Published 27 May 2024 · Updated 2 Dec 2024

Affected packages

silverstripe/frameworkComposer

Affected: >=3.1.9-rc1 <3.1.20
Fixed in: 3.1.20

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.1.20

silverstripe/frameworkComposer

Affected: >=3.2.4-rc1 <3.2.5
Fixed in: 3.2.5

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.2.5

silverstripe/frameworkComposer

Affected: >=3.3.2-rc1 <3.3.3
Fixed in: 3.3.3

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.3.3

silverstripe/frameworkComposer

Affected: >=3.4.0-rc1 <3.4.1
Fixed in: 3.4.1

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.4.1

Details

The core template framework/templates/Includes/GridField_print.ss uses "Printed by $Member.Name".

If the currently logged in members first name or surname contain XSS, this prints the raw HTML out, because Member->getName() just returns the raw FirstName + Surname as a string, which is injected directly.

Is GHSA-r9vp-fp72-xgf7 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.