Bug bounty program
LY
Lyst
Most upvoted reports9
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Subdomain takeover of storybook.lystit.comAnalysed#779442 | Access Control | 2020-01-22 | $1,000 | 163 |
| Web Cache poisoning attack leads to User information Disclosure and moreAnalysed#631589 | Misconfiguration and Insecure Design | 2022-03-22 | – | 45 |
| SSRF at iris.lystit.com#206894 | Server-Side Request Forgery | 2017-10-18 | – | 21 |
| CSRF - Adding unlimited number of saved items via GET request#205953 | Cross-Site Request Forgery | 2017-09-28 | $150 | 19 |
| Site configured improperly at subdomain of lyst.co.uk#208480 | Misconfiguration and Insecure Design | 2017-03-29 | $100 | 19 |
| [https://█████████/]&&[https://█████████/] Open Redirection#537047 | Open Redirect | 2022-03-22 | – | 18 |
| DOM XSS on http://talks.lystit.com#1031644 | Cross-site Scripting | 2021-02-09 | $100 | 15 |
| Mixed Active content issue on https://www.lyst.com#207329 | Misconfiguration and Insecure Design | 2017-02-22 | – | 12 |
| Bypassing one-time checkout router page (revealing payment information)#271176 | Information Disclosure | 2018-05-10 | – | 12 |
Subdomains1,624
| Name | Scope | First seen |
|---|---|---|
| confluence.lystit.comtools | In scope | 2026-11-14 |
| confluence-2020.lystit.comtools | In scope | 2026-11-14 |
| confluence-backup.lystit.comdata, tools | In scope | 2026-11-14 |
| confluence-internal.lystit.cominternal, tools | In scope | 2026-11-14 |
| confluence-staging.lystit.comstaging, tools | In scope | 2026-11-14 |
| jira.lystit.comtools | In scope | 2026-11-14 |
| jira-2020.lystit.comtools | In scope | 2026-11-14 |
| jira-backup.lystit.comdata, tools | In scope | 2026-11-14 |
| jira-internal.lystit.cominternal, tools | In scope | 2026-11-14 |
| jira-staging.lystit.comstaging, tools | In scope | 2026-11-14 |
| plasma-metabase.lystit.comtools | In scope | 2026-11-14 |
| web.plasma-metabase-public.microservices.srv.lystit.comtools | In scope | 2026-11-14 |
1,623 names are covered by the program's own scope; 26 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.