[GH-ISSUE #2056] Potential security vulnerability #673

New issue

Closed

opened 2026-03-16 16:38:49 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 16:38:49 +03:00

Owner

Originally created by @ranjit-git on GitHub (Jan 5, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2056

Is there an existing issue for this?

I have searched the existing issues

Current behavior

security bug

Steps to reproduce

@li Hi a potential security vulnerability has been disclosed to huntr against your repo .
Plz validate this report https://huntr.dev/bounties/5135f71a-8acd-4ac2-ba45-52b1c78155bb

Environment

Production

Version

Cloud

Originally created by @ranjit-git on GitHub (Jan 5, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2056 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior security bug ### Steps to reproduce @li Hi a potential security vulnerability has been disclosed to huntr against your repo . Plz validate this report https://huntr.dev/bounties/5135f71a-8acd-4ac2-ba45-52b1c78155bb ### Environment Production ### Version Cloud

kerem

2026-03-16 16:38:49 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 16:39:05 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jan 5, 2022):

@ranjit-git please give us a little bit of time to triage and resolve the issue before opening up an issue in Github as we do follow huntr.dev reports closely so that we can reduce spam in the repo and also give us a chance to resolve the vulnerability under the hood before a fuilly public disclosure. Hence I am closing this issue and we can continue the conversation over at Huntr.

Also, I have left a comment on Huntr regarding the validity of this report.

Thank you for your effort!

@AndrewBastin commented on GitHub (Jan 5, 2022): @ranjit-git please give us a little bit of time to triage and resolve the issue before opening up an issue in Github as we do follow huntr.dev reports closely so that we can reduce spam in the repo and also give us a chance to resolve the vulnerability under the hood before a fuilly public disclosure. Hence I am closing this issue and we can continue the conversation over at Huntr. Also, I have left a comment on Huntr regarding the validity of this report. Thank you for your effort!