Themata.AI
Follow coverage
Themata.AI

We Took over ChatGPT Accounts

parameter.ai ·

Parameter AI researchers reported a critical ChatGPT web vulnerability that let a malicious public conversation execute attacker-controlled JavaScript in a visitor’s authenticated chatgpt.com session. An attacker could send a normal ChatGPT share link; in the final demonstrated version, simply opening it triggered the exploit after about 4.5 seconds. OpenAI classified the report as P1 and confirmed a fix on October 26, 2026.

The exploit combined ChatGPT’s HTML Preview feature with an interactive graph that loaded MathLive, a math-input library. Although Preview ran in a sandboxed frame on a separate origin, MathLive accepted cross-frame postMessage instructions from any origin to alter a virtual-keyboard layout containing raw HTML. That HTML created an unsandboxed srcdoc iframe inheriting the chatgpt.com origin. ChatGPT’s content-security policy blocked inline scripts but permitted YouTube scripts; researchers used YouTube’s JSONP-style oEmbed callback behavior to execute code.

The injected code could call ChatGPT’s authenticated backend APIs, list recent conversations, retrieve a private conversation never shared with the attacker, and transmit selected data to an external server. OpenAI reproduced the JavaScript execution and private-conversation proof, updated two web frontend versions to reject the MathLive messages, and awarded a $5,000 bounty. The report was submitted October 18 after testing began October 13.

Read original ↗

What people are saying

Commenters treated the story less as an isolated phishing mishap than as an embarrassing security failure for a company asking the world to trust it with conversations, files, and increasingly agentic work.

What readers liked

  • OpenAI accepted the report and repaired both affected ChatGPT frontends, showing that coordinated disclosure can still close a serious…
  • The proof of concept assembled familiar browser primitives into a legible attack chain, giving security engineers a concrete reminder to validate…

Concerns raised

  • A $5,000 reward for a link-driven ChatGPT account takeover looks insulting beside the value of private AI conversations and connected user…
  • Telling users never to click links is not a defense when enterprise email scanners may fetch them automatically and modern authentication routinely…
View discussion ↗
Read full discussion analysis

Source: Hacker News · Based on 15 sampled comments · Analyzed

Discussion overview

Commenters treated the story less as an isolated phishing mishap than as an embarrassing security failure for a company asking the world to trust it with conversations, files, and increasingly agentic work. The reported chain could let a malicious link seize a ChatGPT account, and readers were especially angered that the company valued disclosure at only $5,000. To them, that price signals that finding and responsibly reporting a severe flaw is barely worth the effort, despite the potential exposure of sensitive AI chats and connected workflows.

The thread also pushed back on the easy answer that users should simply avoid links. Email security scanners can automatically follow URLs, while ordinary product emails routinely train people to use login and update links. Several readers argued that systems must withstand those realities rather than outsourcing security to perfect user behavior. Technical commenters corrected speculation that OAuth state handling was necessarily involved, describing the apparent issue instead as an old, preventable cross-window messaging trust failure.

A smaller but sharp line of criticism connected this lapse to OpenAI's claims about powerful coding agents and enormous AI-generated codebases. If frontier programming systems are presented as transformative, commenters expect the company to ship boringly solid security, not repeat web vulnerabilities with account-level consequences. The one bright spot was that the report was accepted and the affected frontends were fixed, with readers appreciating the detailed proof-of-concept chain.

Points of disagreement

The sharp dispute is whether this was mainly a user-click problem or a product-security failure. The first view says no link-clicking habit can be fully safe, but users still bear responsibility; the opposing view notes automated mail scanners and ubiquitous magic-link flows can trigger or normalize the action without meaningful user choice, so the service must make the flow robust. A related disagreement concerns whether low bounties deter reports or deliberately reduce the volume of vulnerabilities a company must handle.

What readers liked

  • OpenAI accepted the report and repaired both affected ChatGPT frontends, showing that coordinated disclosure can still close a serious account-takeover path.
  • The proof of concept assembled familiar browser primitives into a legible attack chain, giving security engineers a concrete reminder to validate cross-window message origins.
  • Readers expect frontier coding agents to raise the floor on production security, and that expectation reflects how consequential AI platforms have become.

Concerns raised

  • A $5,000 reward for a link-driven ChatGPT account takeover looks insulting beside the value of private AI conversations and connected user workflows, weakening incentives for responsible disclosure.
  • Telling users never to click links is not a defense when enterprise email scanners may fetch them automatically and modern authentication routinely relies on emailed magic links.
  • An apparently basic failure to authenticate postMessage senders on a major AI platform makes the product feel less mature than its frontier-model branding.
  • Security lapses land harder because ChatGPT is expanding from a chat tool into a place people may expose files, work context, and agent-enabled access.

Keep reading

  • ChatGPT now lets you lock private chats with a PIN—but forgetting it could erase them for good
  • GPT-6.1 Terra
  • OpenAI starts training its most powerful systems again – but keeps them off the internet out of fear they would go rogue
Sources and details
  • parameter.ai · Published

    We Took over ChatGPT Accounts

    Read report →

Community analysis available for 1 of 1 linked discussions.

Additional discussion searches are still incomplete.

Coverage details and dates

Latest available community analysis:

Summaries: 1 current · 0 awaiting update · 0 not verified

Latest summary update:

Hacker News · parameter.ai

We Took over ChatGPT Accounts ↗
Hacker News discussion ↗

Reported comments: 143 · 15 saved in sample

Analysis ready