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
In reNgine v1.0, there is Stored Cross-site Scripting while deleting an organization in the Organization deletion confirmation modal box!
Steps to Reproduce
Visit your reNgine instance, and login to your account.
Add some targets through the Targets page.
Head over to the /target/list/organization endpoint.
Click on "Add Organization" and write <img src=binit onerror=alert(document.location)> in the Organization name field.
Select targets, and add the organization.
Click on the cross icon under the Action column, which is used for deleting the organization.
You will notice that, while displaying "Are you sure you want to delete {Organization_Name}?", it will render our Organization Name as it is without performing any sort of sanitization, which results in our JavaScript code inside the XSS payload being executed.
This is how this vulnerability can be reproduced.
I have confirmed that this issue can be reproduced as described on a latest version/pull of reNgine: yes
Technical details
Debian 4.19.181-1
The text was updated successfully, but these errors were encountered:
TheBinitGhimire
changed the title
[SECURITY] - Stored Cross-site Scripting while deleting an organization!
[SECURITY] - Stored Cross-site Scripting while deleting an organization in the Organization deletion confirmation modal box!
Aug 20, 2021
Issue Summary
In reNgine v1.0, there is Stored Cross-site Scripting while deleting an organization in the Organization deletion confirmation modal box!
Steps to Reproduce
/target/list/organization
endpoint.<img src=binit onerror=alert(document.location)>
in the Organization name field.You will notice that, while displaying "Are you sure you want to delete {Organization_Name}?", it will render our Organization Name as it is without performing any sort of sanitization, which results in our JavaScript code inside the XSS payload being executed.
This is how this vulnerability can be reproduced.
Technical details
The text was updated successfully, but these errors were encountered: