- Top reward
- Not published
- 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 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 3 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
Screenly may award monetary bounties for valid, previously unreported vulnerabilities.
- Response
-
Within 3 days
Acknowledgement: within 3 business days
- Safe harbor
-
Full
Screenly will not pursue legal action or report your activity to law enforcement.
- Hall of fame
-
Yes
Reports that meaningfully reduce risk but do not qualify for a bounty may still receive recognition (e.g., Hall of Fame mention).
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 6 excluded.
Domains 3
- screenlyapp.com
- screenly.io
- screenly.io (marketing site)
Wildcard domains 2
- *.screenlyapp.com No bounty
- *.screenlyapp.com (web application)
Hardware and IoT 1
- Our digital signage players (Screenly Player / Player Max only )
Out of scope (6)
- Denial-of-service or capacity stress testing
- Known public CVEs without a practical exploit path
- Low-impact issues listed under "Non-Qualifying Issues"
- Social engineering, phishing, or physical attacks against employees, customers, or partners
- Stage and test environments that may reside on the same domains
- Third-party services not owned or controlled by Screenly (e.g., payment providers, CDNs)
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Screenly's policy.
While testing
-
Test only the systems listed in scope
-
Use test or demo accounts
-
Provide minimal proof-of-concept code that demonstrates the vulnerability
-
Exfiltrating or deleting sensitive data
-
Large-scale automated scanning or denial-of-service attempts
-
Phishing, spam, or social engineering of employees or customers
-
Attacks against third-party services
-
If you inadvertently access sensitive data, stop immediately and include only minimal evidence needed to demonstrate the issue in your report.
Not accepted
-
Self-XSS that requires victim input
-
Missing or misconfigured HTTP headers without exploitation impact
-
Version disclosure banners
-
Outdated libraries with no exploitable vulnerability
-
Clickjacking on non-sensitive pages
-
Rate-limit or brute-force issues with negligible impact
-
Chained or multi-issue reports.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.