Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

lemlist

By lempire Vulnerability disclosure program on HackerOne lemlist.com

Accepting reports Full safe harbor
Go to program Website
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
5
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.
Full safe harbor
Good-faith research is authorised; no legal action.
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.

Pays cash
No We do not provide rewards for reported issue. Only fame!
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Hall of fame
Yes We do not provide rewards for reported issue. Only fame!

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

Scope

5 assets you may test, 8 excluded.

Web 5

  • app.lemcal.com Critical No bounty
  • app.lemlist.com Critical No bounty
  • app.lemwarm.com Critical No bounty
  • app.taplio.com Critical No bounty
  • app.tweethunter.io Critical No bounty
Out of scope (8)
  • api.lemlist.com
  • api.taplio.com
  • api.tweethunter.io
  • lemwarm.com
  • taplio.com
  • tweethunter.io
  • www.lemcal.com
  • www.lemlist.com

Rules

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

While testing

  • Please use your own accounts to conduct your research.
  • Do not try to gain access to others' accounts or any confidential information.
  • DO NOT use automated scanning tools
  • Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.
  • You may not publicly disclose the vulnerability prior to our resolution.
  • You provide a working proof of concept that exploits the security issue.

Not accepted

  • Denial of service
  • Spamming
  • Social engineering (including phishing) of lempire staff, contractors or customers
  • Login/Logout CSRF
  • Self-XSS (we require evidence on how the XSS can be used to attack another user)
  • Client-side only vulnerabilities (e.g., HTML injections without persistent or cross-user impact)
  • Miss of rate limits
  • Report from automated tools and scans
  • Vulnerabilities sending spam or unauthorised messages
  • Bugs in 3rd party software
  • X-Frame-Options related
  • Customer's sites
  • Relating to HSTS
  • DNSSEC
  • CAA records
  • Missing security headers which do not lead directly to a vulnerability
  • Theoretical attacks
  • Breaking of SSL/TLS trust
  • Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
  • Password and account recovery policies, such as reset link expiration or password complexity
  • Vulnerabilities without solution on our side (HEIST, ...)
  • Outdated DNS record pointing to system which does not belong to lempire (subdomain takeover)
  • Issue related to homographs
  • HTST preload directive

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 17 minutes 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.

lempire is committed to working with security experts across the globe to stay up to date with the latest security techniques. If you have discovered a security issue that you believe we should know about, we'd welcome working with you. Please let us know about it and we'll make every effort to quickly correct the issue.

Please use your own accounts to conduct your research. Do not try to gain access to others' accounts or any confidential information. When creating accounts, use your hacker email alias, for ex: [email protected]

Disclosure Policy

  • Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
  • Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Reports closed as Informative, Not Applicable or Spam are not disclosed. A duplicate may be disclosed when its original is.

DO NOT use automated scanning tools

Exclusions

While researching, we'd like to ask you to refrain from:

  • Denial of service
  • Spamming
  • Social engineering (including phishing) of lempire staff, contractors or customers
  • Physical access to a lempire user computer
  • Any physical attempts against lempire property or data centers
  • Login/Logout CSRF
  • Self-XSS (we require evidence on how the XSS can be used to attack another user)
  • Client-side only vulnerabilities (e.g., HTML injections without persistent or cross-user impact)
  • Miss of rate limits
  • Report from automated tools and scans
  • Vulnerabilities sending spam or unauthorised messages
  • Bugs in 3rd party software
  • X-Frame-Options related
  • Customer's sites
  • Relating to HSTS
  • DNSSEC
  • CAA records
  • Missing security headers which do not lead directly to a vulnerability
  • Physical attack on the infrastructure
  • Theoretical attacks
  • Breaking of SSL/TLS trust
  • Compromising of browser/device (ex. computer sharing, physical access to a user's device, ...)
  • Vulnerabilities only affecting users of outdated or unpatched browsers and platforms
  • Password and account recovery policies, such as reset link expiration or password complexity
  • Vulnerabilities without solution on our side (HEIST, ...)
  • Outdated DNS record pointing to system which does not belong to lempire (subdomain takeover)
  • Issue related to homographs
  • HTST preload directive
  • Authorizing a third-party OAuth app via our consent screen. Open (dynamic) client registration is by design (it powers the public API and MCP integrations); no token is issued until the user completes a consent screen that WARNS the app is unverified, states access equals sharing their API key, and requires an explicit confirmation. Tricking a user into completing this flow is social engineering / phishing and is out of scope. Still in scope: OAuth flaws granting access WITHOUT informed consent (code/token theft with no consent step, redirect_uri leaks, consent-screen clickjacking, scope escalation)

Scopes

  • Website and API related endpoints on domains listed in program scopes

Eligibility

  • You must be the first reporter of the vulnerability.
  • You follow https://hackerone.com/disclosure-guidelines
  • You do not access data of other users and solely use your created accounts.
  • You may not publicly disclose the vulnerability prior to our resolution.
  • You are not an individual on, or residing in any country on, any U.S. sanctions lists.
  • You provide a working proof of concept that exploits the security issue.

DUPLICATE REPORTS Different exploitation vectors for the same bug or similar bugs may be considered duplicating if the security team believes information provided for a single vector/bug is enough to fix all vectors or bugs reported. A report for a known or duplicating vulnerability is considered as Duplicate. The report can be either a duplicate of another report from any bug bounty platform or a duplicate of the problem internally tracked by the Lempire security team. Usually, access to the original report or some information from the internal task tracker is provided to the reporter of a Duplicate. In some cases, information may not be provided if a Duplicate contains less information or a less critical exploitation vector than the original report. The report is considered duplicated to another report from any bug bounty platform if there is an original report in "New" or "Triaged" state with an earlier report date/time or lower report number, or if it updates the report in "N/A" or "Need more info" state and the original report is in "N/A" or "Need more info" state for less than 1 week, or sufficient information is provided in the original report by the researcher since the report is transferred to "N/A" or "Need more info" state. The report is considered a duplicate of an internal task if there is a task in the internal task tracker which is tracked by the Lempire security team at the time of the duplicate report. Also, public 0-day/1-day vulnerabilities may be considered as a duplicate within a few days after the vulnerability details publication, if the vulnerability is known to our team from public sources and we are working to mitigate or patch it.

Reward

  • We do not provide rewards for reported issue. Only fame!

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep lempire and our users safe!