Skip to content

Optimizely

Bug bounty on Bugcrowd optimizely.com

Accepting reports
Top reward
$3,500
Top severity paid
Critical
Assets in scope
15
Public CVEs
12
Last change

At a glance

What to know before you start testing.

Pays up to $3,500
for critical bugs, from $2,000.
Partial safe harbor
Some legal protection; read the terms.
Public disclosure allowed
You may publish your report.

Rewards

What Bugcrowd lists as the payout for each severity.

Severity Reward
Critical $3,500 from $3,000
High $2,250 from $2,000
Earlier reward tables (1)
  • 11 Nov 2026 to 11 Nov 2026: Critical up to $3,500

Scope

15 assets you may test, 1 excluded.

Web 12

  • https://accounts.cmp.optimizely.com
  • https://accounts.welcomesoftware.com
  • https://analytics.welcomesoftware.com
  • https://app.optimizely.com
  • https://app.welcomesoftware.com
  • https://cdn-app.welcomesoftware.com
  • https://cdn.optimizely.com
  • https://cdn-pci.optimizely.com
  • https://dxc.episerver.net
  • https://optimizely-edge.com
  • https://paasportal.episerver.net
  • https://paasportal.episerver.net/api/v1.0

APIs 3

  • https://api.optimizely.com
  • https://api.welcomesoftware.com
  • https://flags.expeng.optimizely.com
Out of scope (1)
  • https://www.optimizely.com

Rules

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

While testing

  • Accessing private information (so use test accounts)
  • Sending reports and findings from automated tools without verifying them
  • Please share screencasts using a hosted site like a password protected Vimeo, etc.
  • We will not download or view screencast files from file sharing sites like Dropbox due to the security risk of downloading/opening arbitrary files.
  • Researchers are encouraged to sign up for their own developer account here: https://www.optimizely.com/tools/free-feature-flagging#form - using their @bugcrowdninja.com email address on the main Optimizely site.

Not accepted

  • Rendering HTML content without security impact.
  • Triggering emails to be sent to another users account.
  • Pages and content cached after logout.
  • Password complexity requirements.
  • Known CVEs in used 3rd party libraries, without demonstrating how to exploit the vulnerability in the application.
  • Dangling DNS Records - Issues related to stale CNAME records or any other DNS record.
  • Vulnerabilities affecting users of outdated browsers or platforms.
  • Reports relating to email spoofing (inadequate SPF, DKIM and DMARC configurations).
  • Reports related to shared computer accounts.
  • Support system accessed via the 'Provide Feedback' link.
  • Social engineering and any research activities involving our direct customers won't be accepted as valid submissions

Summarised with AI from the program policy on Bugcrowd, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 30 seconds ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Rules updated

    Added: “<p>Researchers are encouraged to sign up for their own developer account here: <a href="https://www.optimizely.com/tools/free-feature-flagging#form" rel="nofoll...”

  2. Scope added

    https://paasportal.episerver.net/api/v1.0/

  3. Scope added

    https://www.optimizely.com/ (out of scope)

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2025-22389 High 8.0 4 Jan 2025
CVE-2025-22390 High 7.5 4 Jan 2025
CVE-2025-22383 Medium 4.6 4 Jan 2025
CVE-2025-22384 High 7.5 4 Jan 2025
CVE-2025-22385 Medium 5.9 4 Jan 2025
CVE-2025-22386 High 7.3 4 Jan 2025
CVE-2025-22387 High 7.5 4 Jan 2025
CVE-2025-22388 Medium 5.7 4 Jan 2025
CVE-2024-56173 Medium 4.7 18 Dec 2024
CVE-2024-56174 High 8.1 18 Dec 2024
CVE-2024-56175 Medium 6.1 18 Dec 2024
CVE-2023-31754 Medium 4.8 14 Nov 2023

Original policy

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

Description

At Optimizely, we're on a mission to help people unlock their digital potential. We do that by reinventing how marketing and product teams work to create and optimize digital experiences across all channels. With our leading digital experience platform (DXP), we help companies around the world orchestrate their entire content lifecycle, monetize every digital experience and experiment across all customer touchpoints. Optimizely has 700+ partners and nearly 1500 employees across our 21 global offices. We live each day with a simple philosophy: large enough to serve, small enough to care.

Targets

Any domain/property of Optimizely not listed in the targets section is out of scope. This includes any/all subdomains not listed above. Social engineering and any research activities involving our direct customers won't be accepted as valid submissions, we highly discourage researchers from involving them, we don't provide authentication, and no, we won't provide credentials. Out-of-Scope www.optimizely.com ​ Depending on their impact, not all reported issues may qualify for a monetary reward. Please refrain from: Denial of Service (DoS) or performing other actions that may negatively affect Optimizely users (spam) Accessing private information (so use test accounts) Sending reports and findings from automated tools without verifying them ​ The following issues are outside the scope of our vulnerability rewards program (either ineligible or false positives): ​ Rendering HTML content without security impact. Rendering HTML content must demonstrate javascript execution or some other malicious action. Triggering emails to be sent to another users account. Pages and content cached after logout. Password complexity requirements. Vulnerabilities in third-party applications or services which use or integrate with Optimizely: help.optimizely.com - Mindtouch, report bugs here community.optimizely.com - Lithium, report bugs here blog.optimizely.com / www.optimizely.com/blog - Wordpress, report bugs here playground.optimizely.com - An internal-only site support.welcomesoftware.com segment.io content.guide.welcomesoftware.com fullstory.com newrelic.com pendo.io Google Analytics typekit.net Vulnerabilities in third-party applications that are integrated with the Optimizely product via developer platform components, such as OAuth and Canvas. Known CVEs in used 3rd party libraries, without demonstrating how to exploit the vulnerability in the application. Dangling DNS Records - Issues related to stale CNAME records or any other DNS record. Vulnerabilities affecting users of outdated browsers or platforms. Reports relating to email spoofing (inadequate SPF, DKIM and DMARC configurations). Reports related to shared computer accounts. Support system accessed via the 'Provide Feedback' link. ​ Generally non-qualifying Web related bug reports have little or no practical significance to product security. Google Bughunter University has a great writeup of bugs that fall into this category - https://sites.google.com/site/bughunteruniversity/nonvuln Target Information The Optimizely platform technology provides A/B testing tools, in which two versions of a web page can be compared for performance, and multivariate testing. Optimizely also enables personalization, which may be used for making data-driven decisions. Access Researchers are encouraged to sign up for their own developer account here: https://www.optimizely.com/tools/free-feature-flagging#form - using their @bugcrowdninja.com email address on the main Optimizely site. For more info regarding @bugcrowdninja email addresses, see here . Focus Areas At Optimizely, security is a key priority. Therefore we invite skilled researchers to participate in our bug bounty program. Below are the 3 focus areas of the program: Web: Optimizely customers embed a small Javascript snippet into their web pages. This javascript is served from a CDN. The javascript contains the logic for the experiments. This is the most sensitive part of our product and we are particularly interested in vulnerabilities related to this snippet. ​ SDK: Optimizely customers embed a small library in their applications. This library contains the logic for the experiments. ​ Editor: Optimizely customers use the editor at app.optimizely.com to manage experiments for their website, such as "does the picture of the blue car or the red car get better user engagement?". Experiment results and account management are also done here. ​ Documentation Documentation that has been provided can be found in the program updates section . Vulnerability types that qualify for the program include Cross-Site Scripting SQL Injection Remote Code Execution Cross-Site Request Forgery Directory Traversal Information Disclosure Content Spoofing Unauthorized Access Privilege Escalation Provisioning Errors ​ You may submit other types of vulnerabilities unless they are listed as out of scope (refer to the VRT for ratings, etc). ​ Please share screencasts using a hosted site like a password protected Vimeo, etc. We will not download or view screencast files from file sharing sites like Dropbox due to the security risk of downloading/opening arbitrary files. This program adheres to the Bugcrowd Vulnerability Rating Taxonomy for the prioritization/rating of findings.