Skip to content

Coursera

Vulnerability disclosure program on HackerOne coursera.org

Accepting reports
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
1
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on HackerOne
Submit through the program page.
Publish after a fix
Coordinate the timing with the company.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Scope

1 asset you may test.

Web 1

  • www.coursera.org Critical No bounty

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Coursera (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please let us know as soon as possible upon discovery of a potential security issue, and we’ll make every effort to quickly correct the issue.
  • Provide us a reasonable amount of time to fix the issue before publishing it elsewhere.
  • Refrain from leaking, manipulating, or destroying any user data.
  • Please only test against accounts you own yourself or with explicit permission of the account holder.
  • Please refrain from automated/scripted account creation.

Not accepted

  • Denial of Service
  • Spamming
  • Standard user enumeration attacks
  • Social engineering our employees, contractors, or users
  • Attempts to access our offices or data centers
  • Reports indicating a lack of rate-limiting on certain APIs
  • Reports solely indicating a lack of a possible security defense such as certificate pinning or two-factor authentication.
  • Reports indicating a lack of DMARC, DKIm or similar protection or identity verification for our email systems.

Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

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

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 hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Security and privacy are top priorities at Coursera. We believe that no technology is perfect and that working with skilled security researchers across the globe is crucial in identifying weaknesses in our technology. If you believe you've found a security bug in our service, we are happy to work with you to resolve the issue promptly.

We consider security issues to be issues when you can perform one or more of the following actions by exploiting a technical problem or misconfiguration on the Coursera platform:

  • Access data that you are otherwise not authorized to access normally as a learner (e.g. accessing other learners' grades or private forum posts).
  • Affects another learner outside of normal interactions on the Coursera platform (e.g. causing scripts to run on another user's browser, changing grades of another user, etc...)
  • Accessing Coursera's internal administrative control systems

Coordinated Disclosure Rules

  • Please let us know as soon as possible upon discovery of a potential security issue, and we’ll make every effort to quickly correct the issue.
  • Provide us a reasonable amount of time to fix the issue before publishing it elsewhere.
  • Refrain from leaking, manipulating, or destroying any user data. Please only test against accounts you own yourself or with explicit permission of the account holder.
  • Please refrain from automated/scripted account creation.

Exclusions

The following activities are not part of the scope of this program:

  • Vulnerabilities on sites hosted by third-parties unless they lead to a vulnerability on the main website (defined as the domains www.coursera.org, class.coursera.org, accounts.coursera.org, and api.coursera.org) or our internal administrative tools.
  • Denial of Service
  • Spamming
  • Standard user enumeration attacks
  • Social engineering our employees, contractors, or users
  • Attempts to access our offices or data centers
  • Reports indicating a lack of rate-limiting on certain APIs
  • Reports solely indicating a lack of a possible security defense such as certificate pinning or two-factor authentication.
  • Reports indicating a lack of DMARC, DKIm or similar protection or identity verification for our email systems. Further posting of these reports will be closed as Spam.

Thanks

We believe in recognizing the work of others. If your work helps us improve the security of our service, we'd be happy to acknowledge your contribution. Thank you for keeping Coursera safe!