Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Fixes #2796 XSS filtering off edit/close links #2803

Closed

Conversation

kmayo-ss
Copy link
Contributor

This is a fix for issue #2796 where the recent 2.4 security fixes have broken the Edit/Close links on the ComplexTableField popup message.
The issue can be replicated by going to File & Images in the CMS backend clicking on the edit icon next to a file to bring up the popup box and clicking save.
This patch resolves this issue.

It has been tested on Chrome, FireFox, Safari and IE9.

I have also noticed that the Popups for ComplexTableField has other broken functionality for example the edit link in the popup goes to a blank page this patch does not resolve this issue and I will raise another issue for this

BUG: Fixes silverstripe#2804 Invalid exit link when saving a ComplextableField Popup
@chillu
Copy link
Member

chillu commented Feb 16, 2014

Closing in favour of #2807. Kirk, invitation to peer review still stands there ;)

@chillu chillu closed this Feb 16, 2014
chillu added a commit to silverstripe-iterators/silverstripe-framework that referenced this pull request Mar 3, 2014
This fixes a limitation introduced through http://www.silverstripe.org/ss-2013-008-xss-in-numericfield-validation/.
Form messages used to accept HTML, now they’re escaped by default, effectively removing the ability
to pass in HTML and take care of escaping manually.

We pass through HTML to message in core through the CTF system, so this needs to be fixed.
It’s an alternative fix to silverstripe#2803.

Conflicts:
	forms/ComplexTableField.php
	forms/Form.php
	forms/FormField.php
	tests/forms/FormTest.php
chillu added a commit to chillu/silverstripe-framework that referenced this pull request Aug 21, 2014
This fixes a limitation introduced through http://www.silverstripe.org/ss-2013-008-xss-in-numericfield-validation/.
Form messages used to accept HTML, now they’re escaped by default, effectively removing the ability
to pass in HTML and take care of escaping manually.

We pass through HTML to message in core through the CTF system, so this needs to be fixed.
It’s an alternative fix to silverstripe#2803.
chillu added a commit that referenced this pull request Aug 22, 2014
This fixes a limitation introduced through http://www.silverstripe.org/ss-2013-008-xss-in-numericfield-validation/.
Form messages used to accept HTML, now they’re escaped by default, effectively removing the ability
to pass in HTML and take care of escaping manually.

We pass through HTML to message in core through the CTF system, so this needs to be fixed.
It’s an alternative fix to #2803.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants