Page 1 of 1
Rejected Due to Clone But Not Clone
Posted: Thu Apr 27, 2023 9:45 am
by _varunsaxena
Found this xss vulnerability , but it was rejected due to clone , but when i checked it is not a clone.
OBB ID : 3277091 , @x1admin please take a look at this.
Re: Rejected Due to Clone But Not Clone
Posted: Thu Apr 27, 2023 12:52 pm
by paras37kumar
If your report on the XSS vulnerability was rejected due to a supposed clone, but you have verified that it's unique, you can reach out to the relevant parties again with evidence to support your claim. When reporting vulnerabilities, use secure communication channels and follow responsible disclosure practices. Additionally, consider using a PBX system to secure your communication channels.
https://freepbx.aavaz.biz/
Re: Rejected Due to Clone But Not Clone
Posted: Thu Apr 27, 2023 1:37 pm
by _varunsaxena
Two of my submissions 3277091 and 3277184 showing under rejected submission with status Clone, but in myprofile section it is showing onHold, Why is that ? @x1admin
Re: Rejected Due to Clone But Not Clone
Posted: Tue Nov 28, 2023 9:58 am
by 0xKayala
Why the XSS report of a subdomain is marked as Clone when it is completely from the main domain and its parameter ?
Re: Rejected Due to Clone But Not Clone
Posted: Thu Dec 21, 2023 4:09 am
by chillyurethra
In the event that your report on the cross-site scripting vulnerability was denied because it was a clone, but you have confirmed that it is unique, you have the opportunity to contact the necessary parties once again with proof to back up your claim.
space bar clicker