Bug bounty program
EV
Evernote
Most upvoted reports9
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Full read SSRF in www.evernote.com that can leak aws metadata and local file inclusionAnalysed#1189367 | Server-Side Request Forgery | 2021-12-06 | – | 264 |
| Wormable stored XSS in www.evernote.com#397968 | No weakness recorded | 2018-08-21 | – | 62 |
| CSRF leads to account deactivation of usersAnalysed#1121990 | No weakness recorded | 2021-10-19 | $300 | 44 |
| 2 click Remote Code execution in Evernote AndroidAnalysed#1377748 | File and Path Handling | 2022-03-29 | – | 30 |
| Non-production Open Database In Combination With XXE Leads To SSRFAnalysed#742808 | Injection and Smuggling | 2020-10-27 | – | 25 |
| One Click Code Execution via FileAnalysed#822609 | Access Control | 2020-03-24 | – | 23 |
| Email Verification Bypass by bruteforcing when setting up 2FAAnalysed#1394984 | Authentication | 2022-05-22 | $150 | 23 |
| [34.96.80.155] Server Logs Disclosure lead to Information LeakageAnalysed#1398270 | Access Control | 2021-12-09 | $150 | 23 |
| Reflected XSS in the shared note view on https://evernote.comAnalysed#1518343 | Cross-site Scripting | 2022-04-20 | $500 | 18 |
Subdomains740
| Name | Scope | First seen |
|---|---|---|
| dev.evernote.comdev | Not in the scope | 2026-11-14 |
| en-dev.evernote.comdev | Not in the scope | 2026-11-14 |
| www.dev.evernote.comdev | Not in the scope | 2026-11-14 |
| stage-dev.evernote.comdev, staging | Not in the scope | 2026-11-14 |
| development.evernote.comdev | Not in the scope | 2026-11-14 |
| staging.dev.evernote.comdev, staging | Not in the scope | 2026-11-14 |
| www.stage-dev.evernote.comdev, staging | Not in the scope | 2026-11-14 |
| public.development.gateways.evernote.comdev | Not in the scope | 2026-11-14 |
| private.development.gateways.evernote.comdev, internal | Not in the scope | 2026-11-14 |
5 names are covered by the program's own scope; 0 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.