TokenController formName not sanitized in hidden input
Published 6 Jun 2024 · Updated 10 Sept 2026
Is your project on an affected sulu/form-bundle?
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
- >=2.0.0 <2.5.3
- Fixed in
- 2.5.3
composer require sulu/form-bundle:^2.5.3Details
Impact
TokenController get parameter formName not sanitized in returned input field leads to XSS.
_What kind of vulnerability is it? Who is impacted?_
Patches
_Has the problem been patched? What versions should users upgrade to?_
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Create a custom Symfony Request listener which checks for the get value of form for the TokenController and if not valid stop the request dispatching and return a error status code.
References
_Are there any links users can visit to find out more?_
Is GHSA-rrvc-c7xg-7cf3 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 sulu/form-bundle, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.