Summary
Cloudflare Agents has a Reflected Cross-Site Scripting (XSS) vulnerability in AI Playground site
A Reflected Cross-Site Scripting (XSS) vulnerability was discovered in the AI Playground's OAuth callback handler. The error_description query parameter was directly interpolated into an HTML script tag without proper escaping, allowing attackers to execute arbitrary JavaScript in the context of the victim's session.
Root cause
The OAuth callback handler in site/ai-playground/src/server.ts directly interpolated the authError value, sourced from the error_description query parameter, into an inline <script> tag.
Mitigation:
- PR: https://github.com/cloudflare/agents/pull/841
- Agents-sdk users should upgrade to
[email protected] - Developers using
configureOAuthCallbackwith custom error handling in their own applications should ensure all user-controlled input is escaped before interpolation.
Credits
Disclosed responsibly by Nishant Kumawat
Impact
An attacker could craft a malicious link that, when clicked by a victim, would:
- Steal user chat message history
- Access all LLM interactions stored in the user's session.
- Access connected MCP Servers
- Interact with any MCP servers connected to the victim's session (public or authenticated/private), potentially allowing the attacker to perform actions on the victim's behalf
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-W5CR-2QHR-JQC5? GHSA-W5CR-2QHR-JQC5 is a medium-severity cross-site scripting (XSS) vulnerability in agents (npm), affecting versions < 0.3.10. It is fixed in 0.3.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of agents are affected by GHSA-W5CR-2QHR-JQC5? agents (npm) versions < 0.3.10 is affected.
- Is there a fix for GHSA-W5CR-2QHR-JQC5? Yes. GHSA-W5CR-2QHR-JQC5 is fixed in 0.3.10. Upgrade to this version or later.
- Is GHSA-W5CR-2QHR-JQC5 exploitable, and should I be worried? Whether GHSA-W5CR-2QHR-JQC5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-W5CR-2QHR-JQC5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-W5CR-2QHR-JQC5? Upgrade
agentsto 0.3.10 or later.