Skip to content

Fourthwall

Bug bounty on security.txt fourthwall.com

Accepting reports security.txt
Top reward
$1,500
Top severity paid
Not published
Assets in scope
8
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to $1,500
top reward, from $50.
Report through their form
vdp.fourthwall.com
Replies within 90 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.

Top reward
$1,500 Depending on the severity of the issue, we offer payments ranging from $50 to $1500 for high-impact and critical vulnerabilities.
Lowest reward
$50 Depending on the severity of the issue, we offer payments ranging from $50 to $1500 for high-impact and critical vulnerabilities.
Response
Within 90 days While we strive to respond as quickly as possible, in some cases, it may take up to three months to provide a complete response.
Hall of fame
Yes Due to our small and growing company, we can sometimes reward reporters with a place in the Hall of Fame and unique swag available only to security researchers.

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

Scope

8 assets you may test, 30 excluded.

Domains 5

  • cdn.fourthwall.com
  • fourthwall.com
  • fourthwall.dev
  • *-shop.fourthwall.com
  • static.fourthwall.com

APIs 1

  • Fourthwall associated services and APIs

Wildcard domains 1

  • *.fourthwall.com

Products and areas 1

  • The Fourthwall website and its associated services, including storefronts and checkouts hosted by Fourthwall
Out of scope (30)
  • Bypassing HTML Sanitization to Make External HTTP Requests on the storefront level by a privileged user
  • Content Spoofing
  • CSV or Formula Injection
  • Disclosure of Server or Software Version Numbers
  • Distributed Denial of Service (DDoS)
  • Enumeration of random identifiers
  • Exploiting Behaviors in Outdated Browsers
  • Flaws Specific to Outdated Browsers or Plugins
  • General Configuration or Policy Suggestions
  • Generic Host Header Attacks
  • Hyperlink Injection is done on the storefront level by a privileged user
  • Insecure Cookie Handling for Account Identifying Cookies
  • Issues with SPF, DKIM, DMARC, CAA, TLSA or DNS Sec Records
  • Missing HttpOnly Flags, Secure Flags, and Browser Cache Vulnerabilities
  • Outputs from Automated Tools
  • Perceived Permission Issues
  • Reports of Broken Links or Unclaimed Social Media Accounts
  • Reports Related to CVV Validation During Payment
  • Reports Related to Permitted Password Strength
  • Self-XSS
  • Slow Requests
  • Social Engineering
  • Spam/Flooding
  • Tab Nabbing
  • Theoretical Subdomain Takeovers
  • Third-Party Security Flaws
  • Usability or UI Issues
  • Vulnerability Scanner False Positives
  • XSS via Inspect Element/Console
  • XSS via Set Header

Rules

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

While testing

  • Do not exploit any discovered security vulnerabilities.
  • Do not access or modify data belonging to other users without their consent.
  • Ensure that your actions do not negatively impact Fourthwall users' experience, such as causing service interruptions or data destruction.
  • Provide Fourthwall with sufficient time to investigate and address the vulnerabilities you report before publicizing them or sharing details with others.

Not accepted

  • Enumeration of random identifiers
  • Tab Nabbing
  • Vulnerability Scanner False Positives
  • Social Engineering
  • Reports of Broken Links or Unclaimed Social Media Accounts
  • Content Spoofing
  • Bypassing HTML Sanitization to Make External HTTP Requests on the storefront level by a privileged user
  • Distributed Denial of Service (DDoS)
  • Exploiting Behaviors in Outdated Browsers
  • Issues with SPF, DKIM, DMARC, CAA, TLSA or DNS Sec Records
  • CSV or Formula Injection
  • Hyperlink Injection is done on the storefront level by a privileged user
  • Insecure Cookie Handling for Account Identifying Cookies
  • Perceived Permission Issues
  • Theoretical Subdomain Takeovers
  • Generic Host Header Attacks
  • Reports Related to CVV Validation During Payment
  • Disclosure of Server or Software Version Numbers
  • Spam/Flooding
  • Reports Related to Permitted Password Strength
  • Missing HttpOnly Flags, Secure Flags, and Browser Cache Vulnerabilities
  • Outputs from Automated Tools
  • General Configuration or Policy Suggestions
  • Flaws Specific to Outdated Browsers or Plugins
  • Slow Requests

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 12 Nov 2026. Last checked 3 hours 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. Reward terms

    The reward table or payout terms were edited

  2. Reward raised

    Maximum no amount → no amount

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.