Report a Vulnerability
Submit, help fixing, get kudos.
Start a Bug Bounty
Run your bounty program for free.
607,985 coordinated disclosures
391,010 fixed vulnerabilities
923 bug bounties with 1,850 websites
18,735 researchers, 1198 honor badges

JAF Development Webshop & CMS Bug Bounty Program

JAF Development Webshop & CMS runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of JAF Development Webshop & CMS

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between JAF Development Webshop & CMS and researchers.

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

General Requirements:

We are very interested in hearing about any potential security issues on our domain

from you. We are happy to thank everyone with a PayPal donation reward, who submits accurate reports which help us improve our web security.

* Please be patient and give us enough time to verify your report.
* Please do not share gathered information with third parties.
* Please provide enough information for us to be able to reproduce your findings. Send as a clear textual description, screenshots and/or PoC. There is no need to actually exploit the website, just describe how we can reproduce. We will then analyze the finding, before we approving it.

As the provided domain is a test/development copy of our live web page, and having an own stack, including database, we can offer testing for several types of vulnerabilities:
* Cross-Site Scripting (XSS)
* Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
* Authentication and Authorization Flaws
* Cross-Site Request Forgery (CSRF)
* Remote Code Execution (RCE)
* Code injections (HTML, JS, SQL, PHP, etc.)
* Insecure direct object references
* Directory Traversal
* Privilege Escalation

Testing Requirements:

There are some things we explicitly ask you not to do:
* If you run automated scans, choose low impact settings (limit requests per minute).
* Do not test using social engineering techniques (phishing, etc.)
* Do not perform DoS or DDoS attacks.
* Do not attack our customers & users, or use any stolen user credentials.

In scope:
This domain is our development instance of our live CMS & Web shop. It is an exact replica of the live page.

Out of scope:
All other companies and services acquired by united-domains are not in scope. That includes other hostnames or other subdomains not listed as in scope. For example there are several similar subdomains like This has the same code page, so please just test the provided subdomain.

Possible Awards:

We are ready to reward you with a PayPal donation for your efforts to improve our web security as a thank you.

Depending on the vulnerability severity (0-10, Low-Critical) the reward will range between 10-100 USD.

We reserve the right to adjust the bounty amount and change the report's vulnerability level accordingly. We also have a total budget, once this is reached, we cannot make any more payout. However, of course we will announce this in advance.

Additional guidelines for rewards:
* Only the first reporter of a vulnerability can be rewarded
* Must be reported via
* No vulnerability disclosure

Please not that the following Vulnerabilities cannot be rewarded:
* Self XSS
* Missing cookie flags
* SSL/TLS best practices
* Mixed content warnings
* DoS or DDoS attacks
* Software version disclosure
* Stack traces or path disclosure
* Vulnerabilities affecting outdated browsers or platforms
* Reports from automated web vulnerability scanners that have not been validated
* Invalid or missing SPF (Sender Policy Framework) records (Incomplete or missing SPF/DKIM/DMARC)

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

Response Time  Information How quickly researchers get responses to their submissions.
Remediation Time  Information How quickly reported submissions are fixed.
Cooperation and Respect  Information How fairly and respectfully researchers are being treated.

Researcher's comments

BhargavRBK     12 October, 2020
hii i had found an bug in your site (
and i had reported it succesfully but the status of the bug is still in manual checking so please provide your email address so we can send the bug details and how to produce it to your email id. Thankq

  Latest Patched


  Latest Blog Posts

05.10.2020 by _r00t1ng_
Steal IP Address using Image
05.10.2020 by _r00t1ng_
DDOS Using SQL injection (SiDDOS)
05.10.2020 by _r00t1ng_
XSS Injection with SQLi
14.09.2020 by aninda_anon
VPS Cheatsheet for bug hunting
14.09.2020 by pk_12397
A Story of IDOR To Account Takeover

  Recent Recommendations

@mako_o9999     23 October, 2020
    Twitter mako_o9999:
Gdattacker found a XSS problem on one of our websites and reported to us. We were able to solve the problem quickly. Thank you so much!
@BizzdoD     21 October, 2020
    Twitter BizzdoD:
Many thanks to Sithu for bringing a XSS vulnerability on our site to our attention. He was very courteous in communications and helped verify that our patch solved the problem properly. Thank you Sir for helping making the Internet a safer place.
@vadus     19 October, 2020
    Twitter vadus:
Warbid helped disclose several vulnerabilities on our website. With his help, we were able to patch this issue and close up the vulnerability. Thank you very much for your help, and thank you for helping to make the web a safer place.
@pagel     18 October, 2020
    Twitter pagel:
Many thanks to cyberaz0r for pointing out a css vulnerability on our site. He was very pleasant to deal with and shared his knowledge openly.
@amswebs     16 October, 2020
    Twitter amswebs:
Thank you for your help with this XSS vulnerability. We appreciate the responsible reporting via openbugbounty.