Skip to content

Automattic

Bug bounty on HackerOne automattic.com

Accepting reports
Top reward
Not published
Top severity paid
Critical
Assets in scope
30
Public CVEs
60
Last change

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report on HackerOne
Submit through the program page.
No public write-ups
Keep findings private.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $1,000
High $600
Medium $300
Low $100
Top reward
$1,000 Critical | $1,000 | $500
Lowest reward
$100 Low | $100 | $100

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

Scope

30 assets you may test, 20 excluded.

Web 18

  • akismet.com Critical
  • api.tumblr.com Critical
  • assets.tumblr.com Critical
  • clay.earth High
  • embed.tumblr.com Critical
  • gravatar.com High
  • intensedebate.com Medium
  • mailpoet.com Critical
  • my.pressable.com Critical
  • parse.ly Critical
  • safe.tumblr.com Critical
  • secure.tumblr.com Critical
  • simperium.com High
  • simplenote.com High
  • t.umblr.com Critical
  • wordpress.com Critical
  • wpscan.com High
  • www.tumblr.com Critical

iOS apps 2

  • com.clay.ios High
  • com.tumblr.tumblr High

Wildcard domains 2

  • *.srvcs.tumblr.com Critical
  • *.tumblr.com Critical

Android apps 1

  • com.tumblr High

Source code 1

  • Jetpack Critical

Products and areas 6

  • Beeper High
  • Crowdsignal Critical
  • WooCommerce Critical
  • WordPress Plugins & Themes Critical
  • WordPress VIP Critical
  • WP Cloud Critical
Out of scope (20)
  • */xmlrpc.php
  • atavist.com
  • happy.tools
  • try.pressable.com
  • *.afterthedeadline.com
  • afterthedeadline.com
  • afterthedeadline.com,*.afterthedeadline.com
  • *.crowdsignal.net
  • *.learnboost.com
  • learnboost.com
  • learnboost.com,*.learnboost.com
  • *.polishmywriting.com
  • polishmywriting.com
  • polishmywriting.com,*.polishmywriting.com
  • *.poll.fm
  • *.scrollkit.com
  • scrollkit.com
  • scrollkit.com,*.scrollkit.com
  • *.survey.fm
  • *.txmblr.com

Rules

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

While testing

  • Access to, or modification of user data is explicitly prohibited without prior consent from the account owner
  • All supporting evidence and other attachments must be stored only within the report you submit
  • Do not host any files on external services
  • please allow Automattic sufficient time to patch other host instances
  • file it within the existing report

Not accepted

  • Broken access control
  • DoS vulnerabilities that are perceived by a lack of rate-limiting or captcha
  • Tabnabbing vulnerabilities
  • Missing Best Practices that don't pose a direct security threat

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

Changes

Tracked since 11 Nov 2026. Last checked 5 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. Scope removed

    Texts

  2. Rules updated

    Added: “…lves trust, unless they demonstrate a high severity impact. Most of the authenticated issues will only be eligible for rep points. For example, a clear path to...”

Public CVEs

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

Search NVD
CVESeverityPublished
CVE-2026-4338 High 7.5 8 Apr 2026
CVE-2023-54332 Medium 5.1 13 Jan 2026
CVE-2024-8009 Medium 4.3 15 May 2025
CVE-2024-6584 Critical 9.1 15 May 2025
CVE-2024-12743 Medium 4.8 15 May 2025
CVE-2024-10076 Medium 5.9 15 May 2025
CVE-2024-10075 Medium 5.6 15 May 2025
CVE-2025-0466 Medium 5.3 4 Feb 2025
CVE-2024-10858 Medium 6.1 25 Dec 2024
CVE-2024-10103 Medium 6.1 19 Nov 2024
CVE-2024-9926 Medium 4.3 7 Nov 2024
CVE-2024-43968 Medium 4.3 1 Nov 2024
CVE-2024-7786 Medium 5.3 4 Sep 2024
CVE-2024-43949 Medium 6.5 29 Aug 2024
CVE-2024-37474 Medium 6.5 4 Jul 2024
CVE-2024-37476 Medium 6.5 4 Jul 2024
CVE-2023-47788 Medium 4.3 19 Jun 2024
CVE-2024-4392 Medium 6.4 14 May 2024
CVE-2023-47774 Medium 5.4 24 Apr 2024
CVE-2024-1310 Medium 4.9 15 Apr 2024
CVE-2023-51489 Medium 5.4 16 Mar 2024
CVE-2023-50875 Medium 6.5 12 Feb 2024
CVE-2023-51488 High 7.1 10 Feb 2024
CVE-2023-51502 High 7.5 5 Jan 2024
CVE-2023-51503 Medium 5.9 31 Dec 2023
CVE-2023-50879 Medium 6.5 29 Dec 2023
CVE-2023-32747 Medium 5.4 21 Dec 2023
CVE-2023-35914 High 7.5 20 Dec 2023
CVE-2023-35915 High 7.6 20 Dec 2023
CVE-2023-35916 High 7.5 20 Dec 2023
CVE-2023-35876 High 8.1 20 Dec 2023
CVE-2023-37871 High 8.2 20 Dec 2023
CVE-2023-47789 Medium 4.3 18 Dec 2023
CVE-2023-47787 Medium 4.3 18 Dec 2023
CVE-2023-49828 Medium 6.5 14 Dec 2023
CVE-2023-47777 Medium 6.5 30 Nov 2023
CVE-2023-45050 Medium 6.5 30 Nov 2023
CVE-2022-3342 High 7.5 20 Oct 2023
CVE-2023-5057 Medium 5.4 16 Oct 2023
CVE-2023-3707 Medium 4.3 16 Oct 2023
CVE-2023-3746 Medium 5.4 16 Oct 2023
CVE-2023-3706 Medium 4.3 16 Oct 2023
CVE-2023-2996 High 8.8 27 Jun 2023
CVE-2023-27429 Medium 5.9 21 Jun 2023
CVE-2014-125104 Medium 6.3 1 Jun 2023
CVE-2023-28121 Critical 9.8 12 Apr 2023
CVE-2022-4497 Medium 5.4 9 Jan 2023
CVE-2022-3919 Medium 4.8 12 Dec 2022
CVE-2022-45069 Medium 6.3 17 Nov 2022
CVE-2022-2034 Medium 5.3 29 Aug 2022
CVE-2022-2080 Medium 4.3 29 Aug 2022
CVE-2022-2386 Medium 6.1 8 Aug 2022
CVE-2017-20086 Medium 6.3 23 Jun 2022
CVE-2021-32789 High 7.5 26 Jul 2021
CVE-2021-24374 Medium 5.3 21 Jun 2021
CVE-2021-24329 Medium 5.4 1 Jun 2021
CVE-2021-24312 High 7.2 1 Jun 2021
CVE-2021-24209 High 7.2 5 Apr 2021
CVE-2020-8215 High 8.8 20 Jul 2020
CVE-2019-11843 Medium 6.1 2 Jun 2020

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.

Automattic runs WordPress.com, Jetpack, WordPress VIP, Beeper, Akismet, Gravatar, WooCommerce, Tumblr, Simplenote, and more. Find a complete list of projects on our website https://automattic.com/.

Please, report vulnerabilities in the WordPress, BuddyPress, or bbPress open-source projects through the WordPress HackerOne page.

Eligibility and Responsible Disclosure

You are responsible for complying with all applicable laws and must only ever use or otherwise access your own test accounts when researching vulnerabilities in any of our products or services. Access to, or modification of user data is explicitly prohibited without prior consent from the account owner.

Any public disclosure of issues prior to resolution may result in disqualification from the program. Individuals who we are legally prohibited from paying, such as those residing in a country on a U.S. sanctions list, are ineligible for rewards.

Rewards

Severity WordPress.com Everything Else
Critical $1,000 $500
High $600 $300
Medium $300 $200
Low $100 $100

The table above outlines the nominal rewards for in-scope assets. Automattic, at its own discretion, will make a final decision on the bounty for qualifying vulnerabilities. Bounties will be awarded to the first reporter of a vulnerability only. If an asset is not in active development, the awards will be adjusted.

Amounts may vary depending upon the severity of the issue and quality of the report.

Crafting a Report

Before submission, please go through the "Non-Qualifying Vulnerabilities" section. If our security team cannot reproduce and verify an issue, a bounty cannot be awarded. To help streamline our intake process, we ask that submissions include:

  • Description of the vulnerability
  • Steps to reproduce the reported vulnerability
  • Proof of exploitability (e.g. screenshot, video)
  • Perceived impact to another user or the organization
  • Proposed CVSSv3 Vector & Score (without environmental and temporal modifiers)
  • List of URLs and affected parameters
  • Other vulnerable URLs, additional payloads, Proof-of-Concept code
  • Browser, OS and/or app version used during testing

Note: Failure to adhere to these minimum requirements may result in the loss of a reward.

All supporting evidence and other attachments must be stored only within the report you submit. Do not host any files on external services.

Same Bug, Different Host

For each report, please allow Automattic sufficient time to patch other host instances. If you find the same bug on a different (unique) host, prior to the report reaching a triaged state, file it within the existing report. Any reports filed separately while we are actively working to resolve the issue will be treated as a duplicate.

Same Payload, Different Parameter

In some cases, rewards may be consolidated into a single payout. For example, multiple reports of the same vulnerability across different parameters of a resource, or demonstrations of multiple attack vectors against a fundamental framework issue. We kindly ask you to consolidate reports rather than separate them.

Qualifying Vulnerabilities

Any reproducible vulnerability that affects the security of our users is likely to be in scope for the program. Common examples include:

  • Cross Site Scripting (XSS)
  • Cross Site Request Forgery (CSRF)
  • Server Side Request Forgery (SSRF)
  • Remote Code Execution (RCE)
  • SQL Injection (SQLi)

Non-Qualifying Vulnerabilities (Out of Scope)

In general, issues requiring authenticated roles will not be eligible. This can include Contributor+, Shop Manager+, or basically a role that could only be awarded by an admin and involves trust, unless they demonstrate a high severity impact. Most of the authenticated issues will only be eligible for rep points. For example, a clear path to admin escalation (RCE, SQL injection). "Broken access control” or being able to perform function of another authenticated role is ineligible, unless a chained escalation to critical/high severity is demonstrated.

We would greatly appreciate you focusing on finding high/critical severity issues: Unauthenticated or customer/subscriber+ with an actual security impact, like unauthenticated stored XSS that can run in other visitors’ or admin’s session, bypass paying for products, or RCE as an example.

We are generally not interested in DoS vulnerabilities that are perceived by a lack of rate-limiting or captcha. As a web-scale service, our threshold for rate limiting is higher than you would probably expect. Of course, if you think you have found an exception to this rule, please let us know.

"Follow-Ups" WooCommerce extension is out of scope.

Cross Site Scripting (XSS) is out of scope for all impactless domains where arbitrary HTML / JavaScript is intentionally allowed, e.g. [blog].tumblr.com, cldup.com etc.

Tabnabbing vulnerabilities are out of scope.

Missing Best Practices that don't pose a direct security threat will most likely not be accepted.

Fine Print

You are expected to comply with all applicable laws in connection with your participation in this program and you are responsible for the payment of any taxes associated with rewards received.