fix(security): scope Optimizely OAuth token postMessage to app origin [] - #11275
Merged
Mitch Goudy (mgoudy91) merged 1 commit intoAug 18, 2026
Merged
Conversation
The OAuth callback broadcast the freshly-minted access token to window.opener with target origin '*', so the browser would deliver it regardless of what origin the opener tab currently held (CWE-346). Typeform, Slack, and Smartling had the same issue fixed under AIS-298; Optimizely was missed.
Mitch Goudy (mgoudy91)
changed the title
Mitch Goudy (mgoudy91)
enabled auto-merge (squash)
August 18, 2026 15:13
Mitch Goudy (mgoudy91)
deleted the
mgoudy/fix-optimizely-postmessage-origin
branch
August 18, 2026 15:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apps/optimizely/src/index.jsx:35) forwarded the freshly-minted access token towindow.openerviapostMessagewith target origin'*', so the browser delivers it regardless of the opener tab's current origin (CWE-346).window.location.origininstead, matching the fix already applied to Typeform, Slack, and Smartling under AIS-298 — Optimizely was missed from that pass.messagelistener in this file already validatesevent.origincorrectly, so this closes the one remaining gap on the send side.Test plan
yarn workspace optimizely test(or repo-equivalent) passes