You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now this is a security issue, as CSRF can occur.
You should consider moving decoupling all forms into an AbstractType and using the SF2 Form component.
One benefit of this is you can re-use forms elsewhere (and so can people who use the library). Also if you bump up the dependency to SF2.6 you can also use bootstrap form theme out the box, so the templates will also be a lot simpler.
The text was updated successfully, but these errors were encountered:
deanc
changed the title
Change all hard-coded forms to use SF2 form component
Security Issue: Change all hard-coded forms to use SF2 form component (avoid CSRF)
Dec 23, 2014
deanc
changed the title
Security Issue: Change all hard-coded forms to use SF2 form component (avoid CSRF)
Security Issue: All forms are vulnerable to CSRF
Dec 23, 2014
Another issue that I stumbled upon today which could be solved by doing this, is that the custom profile fields are only available after account creation. In theory if the registration form were its own type, you could inject the $app object into the AbstractType for the registration form in the constructor, and therefore dynamically add some custom fields based on the available custom fields.
Right now this is a security issue, as CSRF can occur.
You should consider moving decoupling all forms into an AbstractType and using the SF2 Form component.
One benefit of this is you can re-use forms elsewhere (and so can people who use the library). Also if you bump up the dependency to SF2.6 you can also use bootstrap form theme out the box, so the templates will also be a lot simpler.
The text was updated successfully, but these errors were encountered: