LivePerson
Bug bounty on security.txt liveperson.com
- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 4
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 10 days
- As the policy promises.
- Paid by Intigriti
- Proof of identity needed to get paid.
- 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
in an exceptional case, a monetary reward through our managed Bug Bounty Program and platform
- Response
-
Within 10 days
inform you within 10 days whether the submission is accepted or rejected
- Safe harbor
-
Full
Any activities conducted in good faith to comply with all guidelines of this Program will be considered authorized conduct and we will not initiate or recommend legal action against you for such conduct.
- Hall of fame
-
Yes
listing in a LivePerson security hall of fame
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
4 assets you may test, 1 excluded.
Domains 2
- liveperson.com
- liveperson.net
Wildcard domains 2
- *.liveperson.com
- *.liveperson.net
Out of scope (1)
- systems from our vendors
Rules
What the policy asks of you, and the bug types it won't reward, quoted from LivePerson's policy. "We" in these lines means the program, not this site.
While testing
-
Do not perform denial of service attacks, or any attacks that have a reasonable chance of degrading service or customer experience.
-
Do not intentionally view, store, transfer, modify, or destroy data that does not belong to you, and inform us if you have inadvertently accessed or viewed such data.
-
Do not use tools which automate exploit payloads.
-
Do not engage in phishing attacks or other forms of social engineering.
-
Use only [email protected] to submit vulnerability information to us.
-
Only perform testing on in-scope systems and services (see below).
-
Maintain the confidentiality of all information related to your findings and refrain from public disclosure for a reasonable period of time until we have implemented a fix.
-
please do not upload screenshots, videos, or exploit code to a publicly accessible server/repository in preparation of your email, and please do not zip or archive your files.
Not accepted
-
UI and UX bugs and spelling mistakes
-
TLS/SSL related issues
-
SPF, DMARC, DKIM configurations
-
Vulnerabilities due to out of date browsers or plugins
-
Lack of secure flag on cookies
-
Issues that involve a malicious installed application on the device
-
Vulnerabilities requiring a jailbroken device
-
Use of a known-vulnerable library without proof of exploitability
-
Distributed Denial of Service (DDOS) attacks or other brute force attacks
-
Lack of session timeout
-
CSV injection
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 2 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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.