Application-Wide Stored Cross Site Scripting affecting all Users in pandorafms/pandorafms
Nov 3rd 2022
I have found a stored cross-site scripting vulnerability in the reporting dashboard module.
What is stored cross site scripting attack?
Stored XSS, occurs when user supplied input is stored and then rendered within a web page. Typical entry points for stored XSS are: message forums, blog comments, user profiles and username fields. An attacker typically exploits this vulnerability by injecting XSS payloads on popular pages of a site or passing a link to a victim, tricking them into viewing the page that contains the stored XSS payload. The victim visits the page and the payload is executed client side by the victims web browser.
Steps to reproduce:
Create 2 more users apart from admin user. In this scenario
- User1: dev - Group coordinator / Web Group
- User2: lol - Operator (Write) / Web
Payload Used: '"><script>alert("Stored XSS !");alert(document.domain);</script>
1 . Login as User2: lol , go to reporting > dashboard & click on new dashboard button.
2 . Create a new dashboard, select group as "web" , toggle on Favourite tab , click on ok button & intercept the request.
3 . Add above payload in the name parameter & forward the request. Now refresh web page & observe the payload execution.
4 . Next step is to login as dev user & observe the payload execution.
5 . Now login as admin & observe the payload execution (Admin user is also affected with this attack as admin belongs to all the groups by default).
This attack scenario does not require user interaction for the payload execution.
- Perform any action within the application that the user can perform.
- View any information that the user is able to view.
- Modify any information that the user is able to modify.
- Implement security headers such as X-XSS-Protection, CSP for added layer of protection.
- Proper input validation and sanitization should be performed.
- Proper output encoding should be performed.
Hi Team, This issue was found by me & argonx21 in collaboration.
Fixed in v766 --> CVE-2022-45437