Skip to content

Jora

Bug bounty on Bugcrowd jora.com

Accepting reports Full safe harbor
Top reward
$2,500
Top severity paid
Critical
Assets in scope
4
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to $2,500
for critical bugs, from $50.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 5 days
As the policy promises.
Public disclosure allowed
You may publish your report.

Rewards

What Bugcrowd lists as the payout for each severity.

Severity Reward
Critical $2,500 from $1,000
High $1,000 from $500
Medium $500 from $100
Low $100 from $50
Response
Within 5 days For P1/P2 issues, we aim to complete our triage within one business week of the issue being reported.

Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original

Earlier reward tables (1)
  • 11 Nov 2026 to 11 Nov 2026: Critical up to $2,500

Scope

4 assets you may test, 1 excluded.

Wildcard domains 2

  • *.jora.com
  • *.jora.xyz

Android apps 1

  • https://play.google.com/store/apps/details?id=com.jora.android&hl=en_US

iOS apps 1

  • https://apps.apple.com/au/app/jora-jobs-job-search-work/id917565665
Out of scope (1)
  • *.joralocal.com.au

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Jora (via Bugcrowd)'s policy.

While testing

  • DO NOT interact or affect existing customers during testing.
  • Automated vulnerability scanning tools are strictly prohibited.
  • All email addresses belonging to researchers should be your @bugcrowdninja.com.
  • When posting jobs on Jora only post jobs using the following details:
  • DO NOT post jobs into other regions.
  • Please sign up for accounts on https://www.jora.com/ using your @bugcrowdninja.com email address.

Not accepted

  • Cookie flags, i.e. Secure and HTTPOnly.
  • Volume related issues, i.e. brute-force, rate-limiting, and denial of service.
  • Email configuration, i.e. SPF, DKIM, and DMARC.
  • Error pages, i.e. verbose error messages, stack traces, and invalid status codes.
  • Admin or maintenance pages, i.e. monitoring system login pages, and pages with no sensitive information.
  • Clickjacking, i.e. missing X-Frame-Options header.
  • Pre-Authentication Account Takeover.
  • CSRF on unauthenticated resources, i.e. login/logout, pages with anonymous access, and non-sensitive information.
  • Mobile issues that require root access, i.e. credentials in Android SharedPreferences.
  • Non-sensitive exposed API keys, i.e. Google Maps and Raygun.
  • Absent or misconfigured HTTP headers, i.e. Content-Security-Policy, Strict-Transport-Security, X-XSS-Protection and Cache-Control.
  • Configuration that is not directly exploitable, i.e. weak TLS ciphers, password policy, session expiration, and certificate pinning.
  • Vulnerabilities exclusive to outdated, unpatched and unsupported browsers, mobile applications and mobile operating systems.

Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 26 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Rules updated

    Added: “<li>We do not accept reports that contain low-effort or AI-generated content. Submissions must demonstrate original analysis, clear understanding of the issue,...”

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Description

For this program, we're inviting researchers to test Jora's web applications and services - with a focus of identifying security weaknesses that might lead to the compromise of our customer data (mainly, job seekers profiles and resumes). IMPORTANT: Please remember to follow the job posting rules outlined in the program brief. Thank you for participating! Ratings/Rewards: For the initial prioritization/rating of findings, this program will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that a vulnerability priority will be modified due to its likelihood and impact. In any instance where an issue is downgraded, Jora will provide a reasonable justification to the researcher. To maximize your reward and payout time frame, please make sure to include the following in your report: An attack scenario : What is the most likely way an attacker could abuse this vulnerability? Clear reproduction steps : If we can't easily replicate what you are describing, we may not consider the issue as serious. Recommended fix : If you have any good ideas on ways to mitigate the risk without impacting normal users, your submission will have more value. Triage SLA For P1/P2 issues, we aim to complete our triage within one business week of the issue being reported. For other issues, it may take us up to three business weeks to triage the issue.

Targets

Any domain/property of Jora not listed in the targets section is out of scope. This includes any/all subdomains not listed above as well as Jora Local. Access Please sign up for accounts on https://www.jora.com/ using your @bugcrowdninja.com email address. For more info regarding @bugcrowdninja email addresses, see here . Rules for posting a job When posting jobs on Jora only post jobs using the following details: Job Title (must contain): "Bugcrowd - Do Not Apply" Country: United States Business address: 1 Coyote Rd, Teller, Alaska, USA Email: Your @bugcrowdninja.com address DO NOT post jobs into other regions. Jobs posted within United States will be available on the regional Jora sites. Focus areas We are most interested in critical vulnerabilities that allow access to customer PII data (user's profile's and CV's) or Jora corporate data and access to Jora's internal network. Jora includes regionally branded sites (e.g. https://au.jora.com/ or https://us.jora.com/), these all share the same underlying deployment/code and thus will be treated as one site. Rules & Out of Scope DO NOT interact or affect existing customers during testing. This includes things like posting a job not using the instructions above, which could result in real customers applying for your test job ads!! Automated vulnerability scanning tools are strictly prohibited. Jora regularly blocks attacks from users performing suspicious activity. All email addresses belonging to researchers should be your @bugcrowdninja.com. We do not accept reports that contain low-effort or AI-generated content. Submissions must demonstrate original analysis, clear understanding of the issue, and actionable detail. Reports lacking meaningful human input will be rejected. Exclusions Cookie flags, i.e. Secure and HTTPOnly. Volume related issues, i.e. brute-force, rate-limiting, and denial of service. Email configuration, i.e. SPF, DKIM, and DMARC. Error pages, i.e. verbose error messages, stack traces, and invalid status codes. Admin or maintenance pages, i.e. monitoring system login pages, and pages with no sensitive information. Clickjacking, i.e. missing X-Frame-Options header. Pre-Authentication Account Takeover. CSRF on unauthenticated resources, i.e. login/logout, pages with anonymous access, and non-sensitive information. Mobile issues that require root access, i.e. credentials in Android SharedPreferences. Non-sensitive exposed API keys, i.e. Google Maps and Raygun. Absent or misconfigured HTTP headers, i.e. Content-Security-Policy, Strict-Transport-Security, X-XSS-Protection and Cache-Control. Configuration that is not directly exploitable, i.e. weak TLS ciphers, password policy, session expiration, and certificate pinning. Vulnerabilities exclusive to outdated, unpatched and unsupported browsers, mobile applications and mobile operating systems.