Skip to content

Patchstack

Bug bounty on Self-hosted patchstack.com

Accepting reports Full safe harbor
Top reward
$33,000
Top severity paid
Not published
Assets in scope
6
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $33,000
top reward, from $100.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 2 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes Patchstack may, at its sole discretion, offer rewards for valid vulnerability reports.
Response
Within 2 days Initial response: within 2 business days
Safe harbor
Full No legal action against compliant, good faith research
Hall of fame
Yes Public recognition , if desired, following coordinated disclosure

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Reward range in US dollars. Self-hosted's own page has the details.

Scope

6 assets you may test, 5 excluded.

Domains 2

  • patchstack.com
  • patchstack.com/bug-bounty

APIs 1

  • Patchstack APIs and infrastructure

Source code 1

  • Patchstack WordPress plugin and any extensions or integrations developed by Patchstack for other content management systems or platforms

Products and areas 2

  • Any Patchstack-owned digital assets
  • Patchstack website and web applications
Out of scope (5)
  • Denial of Service (DoS) or Distributed Denial of Service (DDoS) attacks
  • Issues in third-party systems, applications, or websites not owned or operated by Patchstack
  • Physical attacks against Patchstack offices, infrastructure, or data centers
  • Social engineering attacks against Patchstack employees, users, or partners
  • Spam, phishing, or content-based abuse

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Patchstack's policy.

While testing

  • Testing must not impact service availability, stability, or performance
  • Automated scanning or high-frequency requests are not permitted without prior written approval
  • Testing must not involve lateral movement, privilege escalation attempts beyond the identified vulnerability, or access to systems outside of scope
  • Any activity that may degrade, disrupt, or interfere with Patchstack services is strictly prohibited
  • Avoid privacy violations, service disruption, and data destruction
  • Access only the data strictly necessary to demonstrate the issue
  • Not access, download, or exfiltrate large volumes of sensitive data
  • Not modify or delete any data
  • Not use social engineering against Patchstack employees or customers
  • Not disclose vulnerabilities publicly prior to resolution

Not accepted

  • Reports generated solely by automated tools without manual validation or a working proof of concept
  • Issues without demonstrable, reproducible impact in a realistic attack scenario
  • Self-XSS or issues that only affect the reporting user without impacting other users, data, or system integrity
  • Issues requiring unrealistic, impractical, or highly unlikely user interaction to exploit
  • Clickjacking or UI redressing issues without demonstrated sensitive actions or impact
  • Lack of rate limiting, brute force protections, or similar controls without a demonstrated exploit scenario or impact
  • Issues that require elevated privileges or roles and do not represent a realistic attack scenario
  • Vulnerabilities reproducible only in non-production, outdated, or artificially modified environments
  • Reports that are not reproducible on the latest production version of the affected system at the time of submission
  • Reports based solely on publicly disclosed vulnerabilities without demonstrating impact on Patchstack systems
  • Testing activities involving unnecessary or excessive collection, storage, or transmission of data

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

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