GHSA-qp29-wcc2-vmpc: Silverstripe HtmlEditor embed url sanitisation
"Add from URL" doesn't clearly sanitise URL server side HtmlEditorFieldToolbar has an action HtmlEditorFieldToolbar#viewfile, which gets called by the CMS when adding a media "from a URL" (i.e. via oembed). This action gets the URL to add in the GET parameter FileURL. However it doesn't do any URL sanitising server side.
Published May 23, 2024
Affected packages
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, < 3.2.1
- Fixed in
- 3.2.1
- Check
composer show silverstripe/framework
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
"Add from URL" doesn't clearly sanitise URL server side
HtmlEditorField_Toolbar has an action HtmlEditorField_Toolbar#viewfile, which gets called by the CMS when adding a media "from a URL" (i.e. via oembed).
This action gets the URL to add in the GET parameter FileURL. However it doesn't do any URL sanitising server side. The current logic will pass this through to Oembed, which will probably reject most dangerous URLs, but it's possible future changes would break this.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-88987
Silverstripe Framework: XSS via XHTML data URI
medium5.4Nov 16, 2026CVE-2026-88988
Silverstripe Framework: XSS via SVG data URI
medium5.4Nov 16, 2026CVE-2026-88989
Silverstripe Framework: Auth bypass GridFieldDetailForm
medium4.3Nov 16, 2026CVE-2026-91112
Silverstripe Framework: CMS_ACCESS_SecurityAdmin privilege escalation
medium6.8Nov 16, 2026CVE-2026-91113
Silverstripe Framework: User-controlled ClassName allows unauthorized record type change
medium4.3Nov 16, 2026CVE-2026-91115
Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter
high8.8Nov 16, 2026
