silverstripe/framework vulnerable to Cross-site Scripting In `OptionsetField` and `CheckboxSetField`

published 2024-05-27 2y ago modified 2024-12-02 last yr.

cvss: 6.1; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

List of key / value pairs assigned to `OptionsetField` or `CheckboxSetField` do not have a default casting assigned to them. The effect of this is a potential XSS vulnerability in lists where either key or value contain unescaped HTML.

Patch / fix

fixed in 1 links 4

packagist silverstripe/framework 3.1.20, 3.2.5, 3.3.3, 3.4.1

Is GHSA-468j-6jrc-2rjx in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
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	silverstripe/framework	>=3.1.19-rc1, <3.1.20 >=3.2.4-rc1, <3.2.5 >=3.3.2-rc1, <3.3.3 >=3.4.0-rc1, <3.4.1	3.1.20 3.2.5 3.3.3 3.4.1

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

GitHub Advisory GHSA-468j-6jrc-2rjx

Fencer Intel 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.