Issue starts after AEM 6.5.23 service pack installation.
The file upload field stopped popping up on the "Upload Zip" option of design importer.
The error is due to sanitization of html which contained a non standard html attribute "coral-fileupload-select".
Is this something adobe should fix as issue is with coral fields which are used in AEM but are non standard?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
hi @Kamal_Kishor,
AEM's XSS protection system sanitizes HTML responses to prevent cross-site scripting attacks. The sanitization is controlled by an attribute allowlist in /libs/granite/ui/components/coral/foundation/clientlibs/foundation/js/xss/xss.js. Maybe after upgrading to SP 6.5.23, the coral-fileupload-select attribute is not included in this allowlist anymore, causing the file upload field to fail to render properly.
Until Adobe releases an official fix, you can implement a workaround by overlaying the XSS configuration file:
Overlay the XSS configuration: Copy /libs/granite/ui/components/coral/foundation/clientlibs/foundation/js/xss/xss.js to /apps/granite/ui/components/coral/foundation/clientlibs/foundation/js/xss/xss.js
Add the missing attribute: Locate the ADD_ATTR array and add "coral-fileupload-select" to the allowlist, similar to other coral attributes already present
Clear browser cache and restart: Clear your browser cache and restart the AEM instance to ensure the changes take effect
References:
hi @Kamal_Kishor,
AEM's XSS protection system sanitizes HTML responses to prevent cross-site scripting attacks. The sanitization is controlled by an attribute allowlist in /libs/granite/ui/components/coral/foundation/clientlibs/foundation/js/xss/xss.js. Maybe after upgrading to SP 6.5.23, the coral-fileupload-select attribute is not included in this allowlist anymore, causing the file upload field to fail to render properly.
Until Adobe releases an official fix, you can implement a workaround by overlaying the XSS configuration file:
Overlay the XSS configuration: Copy /libs/granite/ui/components/coral/foundation/clientlibs/foundation/js/xss/xss.js to /apps/granite/ui/components/coral/foundation/clientlibs/foundation/js/xss/xss.js
Add the missing attribute: Locate the ADD_ATTR array and add "coral-fileupload-select" to the allowlist, similar to other coral attributes already present
Clear browser cache and restart: Clear your browser cache and restart the AEM instance to ensure the changes take effect
References:
@giuseppebaglio : thank you for your inputs. I do not see "coral-fileupload-select" in AEM 6.5.23
Adding this would probably resolve our issue.
I am wondering if this should be fixed from adobe through a hotfix for 6.5.23 or we need to custom fix this for all such instances.
thanks.
Views
Replies
Total Likes
I believe the best course of action is to open a support ticket with Adobe regarding this issue. You can also inquire if my suggestion could serve as a temporary workaround until/if they will release a patch.
@giuseppebaglio : Your suggestions does work for us. And we are in the process if raising a support ticket with adobe as well.
thank you.
Hi @Kamal_Kishor ,
This issue should ideally be fixed by Adobe via an official hotfix rather than a custom change.
After AEM 6.5.23, stricter HTML sanitization removed non-standard attributes like coral-fileupload-select, which are used internally by Coral UI. As a result, the Design Importer’s “Upload Zip” dialog no longer opens because the attribute required by the file upload field is missing.
Since this attribute is part of Adobe’s Coral UI, the issue is a regression in the service pack, not a problem in your code. The correct approach is to log a support ticket with Adobe for a patch.
Temporary client-side workarounds (e.g., re-adding the attribute via JavaScript) are possible but not recommended for production.
In short, this is a product-level issue introduced in 6.5.23, and Adobe should provide an official fix.
Thanks & Regards,
Vishal
@VishalKa5 : Thank you for your response. This does help us with our future course of action. We are in the process of raising a support ticket with Adobe. thanks.
Views
Replies
Total Likes