vulns.co
/
GKData.io MCP and API Buy me a coffee

Meta · Authorization and tenant boundaries

Meta Pixel cross-window handling lost message and token authority

Meta Pixel checked a browser message's origin without fully checking what information the requested operation could disclose or to whom. The researcher reports exposed authorization material and subsequent Instagram takeover with user interaction, alongside a USD 32,500 award. The report does not establish equivalent impact on every site using the script or evidence of real-world abuse.

Read the original writeupUSD 32,500 reported award · Reviewed 2026-10-02

Root cause

A trusted-origin check was treated as a complete access decision. It did not bind the requested operation and recipient to the page data being protected. By tracing browser messages into requests containing page context, the researcher found that sensitive information could pass into a request associated with a different identity.

Demonstrated impact

The researcher reports authorization-material exposure and consequent Instagram takeover with user interaction. Wider script deployment does not establish equivalent impact on every embedding site or evidence of real-world abuse.

What to check for

  • Check the expected sender relationship and message structure, then independently authorize the requested operation and recipient.
  • Define a minimal disclosure contract for analytics and integration messages; omit authentication artifacts from general page context.
  • Review grant-to-client binding separately from message transport and preserve those distinctions in evidence.
  • These are defensive recommendations; the precise vendor patch and the separately alleged grant-binding fix are not independently verified.

Award and evidence

USD 32,500Bug Bounty · Researcher Reported
How the award was verified, and what the record does not establish

One researcher-reported bug bounty, not an event total. The article uses $; prior official Meta program reporting supplies USD context. Actual cash settlement is not established.

  • Researcher-reported award; no independent vendor confirmation or audited transfer.
  • January 2026 page dates may reflect publication or archive migration; original disclosure is not established.
  • USD normalization uses earlier official program context rather than an award receipt.
  • A separate grant-binding flaw is alleged and described as disputed; vendor confirmation and its precise fix date are unverified.

Timeline

Reported
2024-10-16explicit
Awarded
2025-02-12explicit
Fixed
2024-10-24explicit · Overall fix date in the researcher timeline. A separately alleged, disputed grant-binding component has no confirmed fix date; this timestamp does not cover it.

Related visual models

Related cases

All 19 cases in Authorization and tenant boundaries

Sources

  1. Instagram account takeover via Meta Pixel script abuseYoussef Sammouda · reviewed 2026-10-02
  2. Facebook Bug Bounty and BountyCon US-dollar reportingDan Gurfinkel / Facebook · reviewed 2026-10-02

Record reviewed 2026-10-02. Snapshot a066321c166a. Open the complete JSON contract.

Library synced 2026-11-19 · cases last reviewed 2026-10-05

a066321c166a · JSON exports & schemas · CC BY 4.0 content / MIT software