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 |
|---|---|---|
| demo.picsart.studiotest | Not in the scope | 2026-11-14 |
| test.picsart.studiotest | Not in the scope | 2026-11-14 |
| chasebc-uat.picsart.studiotest | Not in the scope | 2026-11-14 |
| iiq-qa-admins.picsart.studiotest | Not in the scope | 2026-11-14 |
| netgenie-test1.com.picsart.studiotest | Not in the scope | 2026-11-14 |
| purpleid-test.corp.picsart.studiointernal, test | Not in the scope | 2026-11-14 |
| ran-oc3-tests.docs.picsart.studiotest | Not in the scope | 2026-11-14 |
| test-api-3t.content.picsart.studioapi, test | Not in the scope | 2026-11-14 |
| test-proj-qa-ew9dox.picsart.studiotest | Not in the scope | 2026-11-14 |
| eddpp-perf.tpe-f5gtm2.picsart.studiotest | Not in the scope | 2026-11-14 |
| 14-fe-test-8dev-okta.dmz.picsart.studioauth, dev, test | Not in the scope | 2026-11-14 |
| sots-publish-uat.team-sales.picsart.studiotest | Not in the scope | 2026-11-14 |
| test-account-blue.mirrorcom.picsart.studiotest | Not in the scope | 2026-11-14 |
| test-mr2.switchtower-sjc-br-1.picsart.studiotest | Not in the scope | 2026-11-14 |
| myworkspace-epa-uat.1picsartcom.picsart.studiotest | Not in the scope | 2026-11-14 |
| profile-service-qa-qa-int.9444com.picsart.studiotest | Not in the scope | 2026-11-14 |
| vpsmeet-clients.test-proj-qa-ew9dox.picsart.studiotest | Not in the scope | 2026-11-14 |
| teslavision-test-inspection.mirrorcom.picsart.studiotest | Not in the scope | 2026-11-14 |
| p13n-health-central.test-proj-qa-ew9dox.picsart.studiotest | Not in the scope | 2026-11-14 |
| zego-qa-int-76-carfax-connection.studio.picsart.studiotest | Not in the scope | 2026-11-14 |
| https-upload-wikimedia-org0-5.test-proj-qa-ew9dox.picsart.studiodata, test | 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.