AI
How We Took Over ChatGPT Accounts
Publication: Simon Willison's Weblog
Author: Not available in collected metadata
Source published: 31/10/2026, 23:15:22 UTC
Briefing created: 01/11/2026, 00:04:06 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 31/10/2026, 23:27:24 UTC.
Briefings
Parameter Labs discovered a critical security flaw in ChatGPT's sandboxed iframe implementation where untrusted HTML content could inject malicious code, allowing attackers to exfiltrate private user data or perform actions on behalf of signed-in users. The vulnerability exploited a complex attack chain involving the MathLive library, iframe messaging, and YouTube oEmbed endpoints, which bypassed OpenAI's Content Security Policy restrictions. OpenAI responded by closing the vulnerability and paying a $5,000 bug bounty, though experts note the payout may have been insufficient for the severity of the risk.
Key points
- Parameter Labs identified a complex attack chain allowing untrusted iframe content to inject malicious code via the MathLive library's virtual keyboard and iframe messaging mechanisms.
- The vulnerability exploited YouTube oEmbed endpoints to execute JavaScript, bypassing OpenAI's Content Security Policy that only allowed scripts from a limited set of domains.
Context
This finding addresses a critical security flaw in OpenAI's ChatGPT implementation where interactive custom HTML apps displayed in sandboxed iframes could be manipulated by untrusted external content. The vulnerability was discovered by Parameter Labs and highlights the risks of bypassing Content Security Policy restrictions through iframe messaging and video embedding endpoints.
Limitations
Evidence covers the discovery of the vulnerability and the initial response by OpenAI. Specific details about the exact impact on user privacy, the timeline of the exploit's usage, and the full scope of data exfiltration capabilities remain unverified.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 01/11/2026, 00:04:06 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeihkxc6fvla6pq2mcxdg5zraf34hbik7spolrq3dptnsliz3vg3nzq