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
First, I want to thank you for developing such an incredible tool. It has been immensely helpful and has streamlined my work significantly.
I would like to suggest a feature enhancement that I believe could benefit many users:
Feature Request:
Add an identifier to each payload that allows users to track the source of an XSS trigger.
Problem Statement:
Currently, when an XSS payload is triggered, especially on internal hosts, it can be challenging to trace back the origin of that payload. This becomes problematic in scenarios where:
The payload was sent a long time ago.
There is no way to associate the trigger with the specific request or script that sent it.
Proposed Solution:
Include unique identifiers (e.g., timestamps, payload IDs, or user-defined labels) with each payload. This identifier could then be logged or displayed alongside the XSS trigger event to provide contextual information.
Benefits:
Makes it easier to trace the origin of a triggered XSS.
Enhances debugging and investigation workflows.
Reduces time spent correlating payloads and triggers.
I hope this suggestion aligns with your vision for the tool and would be happy to provide more details or discuss further if needed.
Thanks again for your efforts and for building such a fantastic tool.
Cheers,
The text was updated successfully, but these errors were encountered:
Hello There
First, I want to thank you for developing such an incredible tool. It has been immensely helpful and has streamlined my work significantly.
I would like to suggest a feature enhancement that I believe could benefit many users:
Feature Request:
Add an identifier to each payload that allows users to track the source of an XSS trigger.
Problem Statement:
Currently, when an XSS payload is triggered, especially on internal hosts, it can be challenging to trace back the origin of that payload. This becomes problematic in scenarios where:
Proposed Solution:
Include unique identifiers (e.g., timestamps, payload IDs, or user-defined labels) with each payload. This identifier could then be logged or displayed alongside the XSS trigger event to provide contextual information.
Benefits:
I hope this suggestion aligns with your vision for the tool and would be happy to provide more details or discuss further if needed.
Thanks again for your efforts and for building such a fantastic tool.
Cheers,
The text was updated successfully, but these errors were encountered: