MediumGHSA-3qh3-54qg-gpq3CVE-2026-88989

Silverstripe Framework: Auth bypass GridFieldDetailForm

Published 16 Nov 2026 · Updated 16 Nov 2026

Is your project on an affected silverstripe/framework?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<6.2.13
Fixed in
6.2.13
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^6.2.13

Details

Impact

A CMS user who can edit records through a GridField detail form could create new records without the permission to create them, by sending a save request directly.

Reported by

HDWSec - https://hdwsec.fr

Is GHSA-3qh3-54qg-gpq3 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.

More advisories for silverstripe/framework

  • HighCVE-2026-91115Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter · 16 Nov 2026
  • MediumCVE-2026-91113Silverstripe Framework: User-controlled ClassName allows unauthorized record type change · 16 Nov 2026
  • MediumCVE-2026-91112Silverstripe Framework: CMS_ACCESS_SecurityAdmin privilege escalation · 16 Nov 2026
  • MediumCVE-2026-88988Silverstripe Framework: XSS via SVG data URI · 16 Nov 2026
  • MediumCVE-2026-88987Silverstripe Framework: XSS via XHTML data URI · 16 Nov 2026
  • MediumCVE-2026-54720Silverstripe Framework: Possible XSS attack through media embed · 27 Aug 2026
All 99 advisories for silverstripe/framework

References

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