Contact us
← Article questionsWhat should we do?

CVEHit Business Advisory by IntegrityLab.ai

What should we do?

Optimizely Web Experimentation JavaScript incident: Business Triage

Do Now

  • Security owner: preserve current and historical Optimizely snippets, project History and relevant logs.
    What to ask

    Keep copies before anyone edits or cleans up projects. Record the date, source and person for each item.

  • Provider: ask Optimizely to confirm whether our listed project IDs were affected, and in which time windows.
    What to ask

    Send the project IDs from the page inventory. Ask for written scope and for any account activity on those projects. Keep the reply as evidence.

  • Application owner: decide whether to disable Optimizely on sensitive surfaces until scope is verified.
    What to ask

    Weigh the loss of experiments against the uncertainty. Coordinate the change with the Security owner and record the decision and date.

Do Next

  • Security owner: review whether sensitive pages use an enforced Content Security Policy, not report-only.
    What to ask

    Blocking one external host alone is not complete protection, because the source describes an embedded payload fallback. Review the whole policy for script sources and where pages can send data.

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…