Security is top priority at Judge.me. We constantly release new features and no system is perfect. We look forward to working with the security community around the world to find vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Judge.me will make a best effort to meet the following SLAs for hackers participating in our program:

| Type of Response | SLA in business days |

| ------------- | ------------- |

| First Response | 2 days |

| Time to Triage | 2 days |

| Time to Bounty | 14 days |

| Time to Resolution | depends on severity and complexity |

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• Please do not discuss any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.

• Follow HackerOne's disclosure guidelines.

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

• Automated scanning is prohibited as it almost certainly doesn't reveal any vulnerabilities, while strips many of our system alerts and may negatively affect our system's performance.

• Do not write test reviews on our customer websites, instead, write reviews on your test store, or on one of our test stores.

• Do not write test reviews on the app store of ecommerce platforms since this may violate the platform's policy.

• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.

• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).

• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.

• Social engineering (e.g. phishing, vishing, smishing) is prohibited.

• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

Test Plan

You can create a test account on your own easily using the following instructions. Please ensure that you register accounts using your @wearehackerone email alias.

There are two types of users in our system: Reviewer (aka Buyer) and Shop (aka Merchant).

Reviewer

• To register: simply use your email to write a review on any product page with our review widget on.

• To log in: fill in your email in our login page and we will send you an email with magic link to log in.

Merchant

To register:

1. Create a Shopify Partner account. A Shopify Partner account can have unlimited number of Shopify development stores.

2. Within your Shopify Partner account, create a development store

3. Go to our login page, fill in your Shopify domain (e.g. xxx.myshopify.com), accept a few steps (don't forget to check the terms and the app permissions ;).

4. Optionally, you can upgrade to our Awesome paid plan. It will be free (the charge will be just a test charge) as our apps are "partner-friendly" (meaning any Shopify development store can upgrade for free).

To log in:

Simply go to the Apps page in your Shopify store Admin (e.g. xxx.myshopify.com/admin/apps), and click on our apps.

Rewards

Our rewards are based on severity per CVSS (the Common Vulnerability Scoring Standard). Please note these are general guidelines, and reward decisions are up to the discretion of Judge.me.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Clickjacking on pages with no sensitive actions

• Self-XSS which is not directly exploitable or would require convincing the user to copy/paste the JavaScript payload

• Text injection or Content spoofing in our 404-not-found page (example)

• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions

• Attacks requiring MITM or physical access to a user's device.

• Previously known vulnerable libraries without a working Proof of Concept.

• Comma Separated Values (CSV) injection without demonstrating a vulnerability.

• Missing best practices in SSL/TLS configuration.

• Any activity that could lead to the disruption of our service (DoS).

• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS

• Rate limiting or bruteforce issues on non-authentication endpoints

• Missing best practices in Content Security Policy.

• Missing HttpOnly or Secure flags on cookies

• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)

• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]

• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. application or server errors).

• Disclosure of server or software version numbers

• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.

• Tabnabbing

• Open redirect - unless an additional security impact can be demonstrated

• Issues that require unlikely user interaction

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Judge.me and our users safe!