Cross-site Scripting (XSS) - Stored in orchardcms/orchardcore
Jan 6th 2022
The application does not escape special characters before output to FE, lead to stored XSS.
Proof of Concept
Example of a case:
Go to Content > Content Types
Create or edit a type with XSS payload into
Display Namefield, e.g:
Social Meta Settings </title><svg/onload=alert('hacked')><title>
Tick on the
- Save and go to create new Type which edited above or go to Content > Content Items. Script will triggered
XSS can have huge implications for a web application and its users. User accounts can be hijacked, change the html screen and insult the organization. Credentials could be stolen, sensitive data could be exfiltrated, and lastly, access to your client computers can be obtained.
@maintainer your patch has not patched all locations. For example in the Workflows section, maybe I'll try to list them all in the next report