Automattic · disclosed reports
Information Disclosure
11 disclosed reports · $0 paid · 10 valid · 1 informative
Every dot is a report; the named ones are the most upvoted. Bright dots were paid a bounty. A report opens its page here: our analysis where there is one, and the link to HackerOne. The status is HackerOne's own outcome; "access needed" is only what a title states.
Open Automattic on HackerOne- reports
- 11
- valid
- 10
- paid a bounty
- 0
Every one of the 11 is a mark on the map. Named now: 1 to 11, most upvoted first.
- Unauthenticated access to webmail at maildev.happytools.dev leading to compromised wordpress site api.happytools.dev [RCE]
- Disclosure of 152 cookie names via crafted input
- SSRF and local file disclosure in https://wordpress.com/media/videos/ via FFmpeg HLS processing
- Able to comment/view in others support ticket at https://en.instagram-brand.com/requests/dashboard
- Wordpress VIP leaks email of the test a/c
- Unauthenticated Private Messages DIsclosure via wordpress Rest API
- information disclosure lead to disclose users private notes
- An Automattic employee's GitHub personal access token exposed in Travis CI build logs
- De-anonymize anonymous tips through the Tumblr blog network
- Serving Transitions From: HTTP Protocol (not secure)
- information disclosure
paid a bounty
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.