Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Payload Unique Identifier #190

Open
Sicks3c opened this issue Dec 4, 2024 · 0 comments
Open

[Feature Request] Payload Unique Identifier #190

Sicks3c opened this issue Dec 4, 2024 · 0 comments

Comments

@Sicks3c
Copy link

Sicks3c commented Dec 4, 2024

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:

  • 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,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant