Bug bounty program
PI
Picsart
Most upvoted reports1
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| User account compromised authentication bypass via oauth token impersonationAnalysed#739321 | Access Control | 2020-03-20 | – | 101 |
Subdomains1,101
| Name | Scope | First seen |
|---|---|---|
| api.picsart.studioapi | Not in the scope | 2026-11-14 |
| api-glb-bln.picsart.studioapi | Not in the scope | 2026-11-14 |
| my-api.9444com.picsart.studioapi | Not in the scope | 2026-11-14 |
| test-api-3t.content.picsart.studioapi, test | Not in the scope | 2026-11-14 |
| ec2-lux-api-hkg60.ro.picsart.studioapi | Not in the scope | 2026-11-14 |
| origin-api-b2b.99com.picsart.studioapi | Not in the scope | 2026-11-14 |
| lon2-webservice-a7.99com.picsart.studioapi | Not in the scope | 2026-11-14 |
| vpnbeta-webservices.app-com.picsart.studioapi | Not in the scope | 2026-11-14 |
| origin-presearch-api.fewr1-1.picsart.studioapi | Not in the scope | 2026-11-14 |
| dev-esp-notifications-api.app.picsart.studioapi, dev | Not in the scope | 2026-11-14 |
| prod-engine-gke-asia-east1-c-api.cms1.picsart.studioadmin, api | Not in the scope | 2026-11-14 |
0 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.