Skip to content

Picsart

Vulnerability disclosure program on HackerOne picsart.com

Accepting reports Full safe harbor
Top reward
No cash rewards
Top severity paid
Critical
Assets in scope
18
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 2 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What HackerOne lists as the payout for each severity.

This program does not pay cash rewards.

Pays cash
No We do not offer a bug bounty at this time, but certain vulnerabilities with a working proof of concept on our Android mobile app may qualify for a bounty through the Google Play Security Rewards Program.
Response
Within 2 days Time to First Response: 2 business days
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

18 assets you may test.

Web 15

  • ai.picsart.com Critical No bounty
  • api.picsart.com Critical No bounty
  • api.picsart.io Critical No bounty
  • cdn-basic-content-api.picsart.io Critical No bounty
  • console.picsart.io Critical No bounty
  • content-discovery.picsart.io Critical No bounty
  • demo.sdk.picsart.io Critical No bounty
  • optifyr.com Critical No bounty
  • picsart.io Critical No bounty
  • revenue-tracking.picsart.io Critical No bounty
  • stage.optifyr.com Critical No bounty
  • t.picsart.com Critical No bounty
  • upload.picsart.com Critical No bounty
  • video-api.picsart.io Critical No bounty
  • www.picsart.com Critical No bounty

Android apps 1

  • com.picsart.studio Critical No bounty

Desktop and binaries 1

  • 9WZDNCRFJ10M Critical No bounty

iOS apps 1

  • 587366035 Critical No bounty

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Picsart (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with the explicit permission of the account holder.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Do not perform DoS or DDoS attacks.
  • Do not run automated scans without checking with us first.

Not accepted

  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • Absence of certificate pinning
  • Lack of obfuscation
  • Lack of binary protection control in Android app
  • Runtime hacking exploits using tools like but not limited to Frida/ Appmon (exploits only possible in a jailbroken environment)

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 17 minutes 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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Picsart is an all-in-one photo and video editing app for making the social content pop. With 130 million monthly creators, Picsart spans the globe. And that is why we take Security, Trust, and Transparency seriously.

Picsart looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Picsart will make a best effort to meet the following response targets for hackers participating in our program:

  • Time to First Response: 2 business days
  • Time to Triage: 2 business days
  • Time to resolution: Up to 45 business days, depending on the severity and complexity.

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

If you have identified a potential security vulnerability in our technology, please submit us a detailed report with reproducible steps. Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

Program Rules

  • Please provide detailed and clear reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.
  • Do not perform DoS or DDoS attacks.
  • Do not run automated scans without checking with us first. They are often very noisy.

#Out of Scope Vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Clickjacking on pages with no sensitive actions.
  • Unauthenticated/logout/login CSRF.
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices in SSL/TLS configuration.
  • Any activity that could lead to the disruption of our service (DoS).
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • Absence of certificate pinning
  • Lack of obfuscation
  • Lack of binary protection control in Android app
  • Runtime hacking exploits using tools like but not limited to Frida/ Appmon (exploits only possible in a jailbroken environment)

Rewards

We do not offer a bug bounty at this time, but certain vulnerabilities with a working proof of concept on our Android mobile app may qualify for a bounty through the Google Play Security Rewards Program. To see which apps and vulnerabilities may qualify for a bounty, please refer to the Google Play Security Rewards Program’s Scope and Vulnerability Criteria.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Picsart and our users safe!