We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Expected behavior would be to display the URLs, with extra handling to account for the links having XSS payloads
scan an XSS vulnerable site like this one when you go to view the vulnerabilities....have fun clicking out of several pop up boxes that got injected
- reNgine: - OS: - Python: - Docker Engine: - Docker Compose: - Browser:
No response
The text was updated successfully, but these errors were encountered:
Hey @Rho-9-Official! 👋 Thanks for flagging this bug! 🐛🔍
You're our superhero bug hunter! 🦸♂️🦸♀️ Before we suit up to squash this bug, could you please:
📚 Double-check our documentation: https://rengine.wiki 🕵️ Make sure it's not a known issue 📝 Provide all the juicy details about this sneaky bug
Once again - thanks for your vigilance! 🛠️🚀
Sorry, something went wrong.
Hi @Rho-9-Official do you mind submitting this via https://github.com/yogeshojha/rengine/security It will be easier for me to manage security reports from there and maybe we could assign you a CVE ID as well.
Thanks
Reported as security report
No branches or pull requests
Is there an existing issue for this?
Current Behavior
Honestly this one explains it all, but I was scanning a site upon request, and found they're vulnerable to XSS....and so is RengineExpected Behavior
Expected behavior would be to display the URLs, with extra handling to account for the links having XSS payloads
Steps To Reproduce
scan an XSS vulnerable site like this one
when you go to view the vulnerabilities....have fun clicking out of several pop up boxes that got injected
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: