CVE-2024-37156: TokenController formName not sanitized in hidden input
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?
Other sources
The SuluFormBundle adds support for creating dynamic forms in Sulu Admin. The TokenController get parameter formName is not sanitized in the returned input field which leads to XSS. This vulnerability is fixed in 2.5.3.
— NVD
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-37156?
CVE-2024-37156 has a moderate severity level due to the potential for cross-site scripting (XSS) attacks.
How do I fix CVE-2024-37156?
To fix CVE-2024-37156, upgrade to version 2.5.3 or later of the sulu/form-bundle.
Who is impacted by CVE-2024-37156?
Any application that uses the sulu/form-bundle version between 2.0.0 and 2.5.3 is impacted by CVE-2024-37156.
Are there any workarounds for CVE-2024-37156?
Currently, there are no effective workarounds for CVE-2024-37156 other than upgrading the affected software.
What does CVE-2024-37156 vulnerability exploit?
CVE-2024-37156 exploits a lack of input sanitization in the TokenController's formName parameter, leading to XSS vulnerabilities.