Infosec Institute

Open Bug Bounty mentioned in the
Top 6 Bug Bounty programs of
2022 by the InfoSec Institute

The Hacker News

Open Bug Bounty named among the
Top 5 Bug Bounty programs of 2021
by The Hacker News

For security researchers
Report a Vulnerability
Submit, help fixing, get kudos.
For website owners
Start a Bug Bounty
Run your bounty program for free.
1,765,886 coordinated disclosures
1,456,851 fixed vulnerabilities
2,070 bug bounty programs, 3,981 websites
55,097 researchers, 1,726 honor badges

Are you sure you want to delete the vulnerability?

Yes No

This feature enables you to send additional notifications to the website owners or admins after the vulnerability is submitted. The total number of additional notification is limited to 10, and to 1 in 24 hours.

Notify specific security contact:


To my best knowledge this email belongs to the website owner/admin


kloesterl-shop.de Cross Site Scripting Vulnerability
Report ID: OBB-3994134

Security Researcher Dipu1A Helped patch 16678 vulnerabilities
Received 9 Coordinated Disclosure badges
Received 63 recommendations
, a holder of 9 badges for responsible and coordinated disclosure, found Cross Site Scripting security vulnerability affecting kloesterl-shop.de website and its users.

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 hidden ("On Hold") to give the website operator/owner sufficient time to patch the vulnerability without putting any of its systems or users at risk. Once patched, vulnerability details can be publicly disclosed by the researcher in at least 30 days since the submission. If for a reason the vulnerability remains unpatched, the researcher may disclose vulnerability details only after 90 days since the submission.

Affected Website:kloesterl-shop.de  
Open Bug Bounty Program:Create your bounty program now. It's open and free.
Vulnerable Application:[hidden until disclosure]
Vulnerability Type:XSS (Cross Site Scripting) / CWE-79
CVSSv3 Score:[hidden until disclosure]
Disclosure Standard:Coordinated Disclosure based on ISO 29147 guidelines
Discovered and Reported by:Dipu1A Helped patch 16678 vulnerabilities
Received 9 Coordinated Disclosure badges
Received 63 recommendations
Remediation Guide:OWASP XSS Prevention Cheat Sheet

Coordinated Disclosure Timeline

Vulnerability Reported:19 November, 2024 10:00 GMT
Vulnerability Verified:19 November, 2024 10:10 GMT
Website Operator Notified:19 November, 2024 10:10 GMT
a. Using the ISO 29147 guidelines
b. Using publicly available security contacts
c. Using Open Bug Bounty notification framework
d. Using security contacts provided by the researcher
Public Report Published [without technical details]:19 November, 2024 10:10 GMT
Scheduled Public Disclosure:  InformationA security researcher can delete the report before public disclosure, afterwards the report cannot be deleted or modified anymore. The researcher can also postpone public disclosure date as long as reasonably required to remediate the vulnerability.17 February, 2025 10:00 GMT

For Website Operators and Owners

Please read how Open Bug Bounty helps make your websites secure and then contact the researcher directly to get the vulnerability details. The researcher may also help you fix the vulnerability and advice on how to prevent similar issues:

How it works and what's next

For remediation best practices, please also refer to OWASP remediation guidelines. More information about coordinate and responsible disclosure on Open Bug Bounty is available here.

DISCLAIMER: Open Bug Bounty is a non-profit project, we never act as an intermediary between website owners and security researchers. We have no relationship or control over the researchers. Our role is limited to independent verification of the submitted reports and proper notification of website owners by all reasonably available means.

kloesterl-shop.de

Website Overview and Rating

SSL/TLS Server Test:A    View Results
Web Server Security Test:C    View Results
Malware Test:Click here
Domain Health Report:Click here

Latest Submissions

OBB-ID Reported by Status Reported on
On Hold
19.11.2024
unpatched
03.06.2023

  Latest Patched

 05.12.2024 novaveneza.sc.gov.br
 05.12.2024 sanduskycountyoh.gov
 05.12.2024 ervalvelho.sc.gov.br
 05.12.2024 barrabonita.sc.gov.br
 05.12.2024 guabiruba.sc.gov.br
 05.12.2024 bomretiro.sc.gov.br
 05.12.2024 calmon.sc.gov.br
 05.12.2024 mrmcw.edu.in

  Latest Blog Posts

04.12.2023 by BAx99x
Unmasking the Power of Cross-Site Scripting (XSS): Types, Exploitation, Detection, and Tools
04.12.2023 by a13h1_
$1120: ATO Bug in Twitter’s
04.12.2023 by ClumsyLulz
How I found a Zero Day in W3 Schools
04.12.2023 by 24bkdoor
Hack the Web like a Pirate: Identifying Vulnerabilities with Style
04.12.2023 by 24bkdoor
Navigating the Bounty Seas with Open Bug Bounty

  Recent Recommendations

    2 December, 2024
    mrmnm:
Thank you very much for finding and disclosing a XSS vulnerability in my webpage, so I could fix it immediately.
    25 November, 2024
    JoDesp:
Thanks for reporting the XSS problem and for the friendly and quick email contact.
    18 November, 2024
    danielvoigt01:
Dear Fatima0454,

Thank you very much for taking the time to report the XSS vulnerability on our not profit association's website. Your detailed report allowed us to quickly identify and resolve the issue. Thanks to your efforts, you've made not only our website but the web as a whole a little safer.

We truly appreciate your commitment to responsible disclosure and your contribution to improving online security. Please don’t hesitate to reach out again if you notice anything else or have further suggestions.

Best regards
Daniel
    18 November, 2024
    merlu:
Received a message via one of my customers about an XSS vulnerability found by SYPltd, after contacting the researcher I got a good report detailing the problem.

Communication was quick and professional. Thankfully we could swiftly fix this issue ourselves. Great thanks to you SYPltd for making us aware of the problem.
    4 November, 2024
    Prabu:
Thank you for your timely help with quick response.