6 matches found
kamus.net Cross Site Scripting vulnerability OBB-3923300
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
kamus.net Cross Site Scripting vulnerability OBB-3860682
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
kamus.net Cross Site Scripting vulnerability OBB-3789503
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
kamus.net Cross Site Scripting vulnerability OBB-3731124
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
kamus.net Cross Site Scripting vulnerability OBB-3286752
Following the coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has: a. verified the vulnerability and confirmed its existence; b. notified the website operator about its existence. Technical details of the vulnerability are currently hidde...
Unfixed XSS vulnerability at kamus.net
Security researcher YS, has submitted on 29/03/2008 a cross-site-scripting XSS vulnerability affecting kamus.net, which at the time of submission ranked 19527 on the web according to Alexa. We manually validated and published a mirror of this vulnerability on 03/04/2008. It is currently unfixed. ...