Browse / AI Framework and Platform Flaws / Cross-site scripting
Cross-site scripting
68 records in AI Framework and Platform Flaws.
- Kubeflow Pipelines: Reflected XSS in the frontend pod information and events error responses Pod name and namespace query values are echoed unescaped into HTML error responses, so a crafted link runs script in the frontend origin.
- LiteLLM vulnerable to reflected XSS in /sso/debug/callback An identity provider returns a display name containing a closing script tag, which the unauthenticated SSO debug callback reflects into inline script and executes.
- Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin A terminal port preview iframe keeps same-origin access, so script served from a previewed port runs in the app origin and steals sessions.
- Open WebUI: Same-origin XSS to account takeover via terminal file-preview iframe hardcoding allow-same-origin Terminal-served HTML previews run in an iframe that grants same-origin access, so scripts in the file run in the app origin and can read the session token.
- n8n: Stored DOM XSS via Resource Locator `cachedResultUrl` A workflow's cachedResultUrl is passed to window.open without scheme checks, so a javascript URL runs script when a victim opens it.
- Open WebUI allows limited stored XSS vila uploaded html file A low-privileged user uploads an HTML file containing script that runs in another user's browser when the file is opened.
- Open WebUI: Stored XSS to Account Takeover via Model Profile Images Model profile image uploads accept SVG data URIs that earlier fixes missed, so embedded scripts run when the image URL is opened.
- Open WebUI: Stored XSS in Mermaid Markdown Preview A Markdown file with a Mermaid click directive carrying a javascript: URL is rendered into the DOM unsanitised, so script runs when the preview opens.
- n8n: Stored XSS in Chat Trigger Node A user with workflow edit rights sets a malicious webhook ID that injects script into the chat page, which then runs for anyone who opens it.
- n8n: Reflected XSS via Facebook, WhatsApp, and Microsoft Teams Trigger Webhook Verification Endpoints A webhook verification endpoint echoes a query parameter into the response without escaping or CSP, so a crafted link runs script in the app origin.
- n8n: Same-Origin XSS in Respond to Webhook Node A binary response path serves attacker-chosen content types without the sandbox header, so a public webhook runs scripts in the application origin.
- Open WebUI has XSS via SVG in /api/v1/channels/webhooks/{webhook_id}/profile/image A webhook profile image URL accepts an SVG data URI that is served unsanitised as image/svg+xml, so embedded script handlers run in the app origin.
- Open WebUI vulnerable to stored XSS via OAuth picture claim stored as SVG data URI in profile_image_url The OAuth login path stores a remote picture as an SVG data URI that skips the image validator and is served inline, so its script runs on the app origin.
- Open WebUI has Stored Cross-Site Scripting In Profile Picture Profile image data URIs with arbitrary MIME types are served from the app origin, so an embedded SVG script runs for anyone who views the image.
- Open WebUI has stored XSS via unsanitized Office/Excel/DOCX file preview rendering ({@html} without DOMPurify) Office file previews are rendered as raw HTML without sanitisation, a regression of an earlier fix, so uploaded documents can run script.
- Open WebUI has stored XSS via attacker-controlled file extension in /api/v1/audio/transcriptions A polyglot WAV/HTML file uploaded with an HTML extension is served as text/html from the cache route, so embedded scripts run in the app origin.
- Open WebUI has Stored XSS in Banner Component via Improper Sanitization Order Banner content is sanitised before Markdown conversion, so a link produced afterwards carries a javascript: URL that is rendered unescaped.
- Open WebUI has Stored XSS in Pending User Overlay via Incorrect DOMPurify Application Order Running the sanitiser before Markdown parsing lets javascript: links created during parsing reach the page unfiltered, enabling stored script execution.
- open-webui Vulnerable to Stored XSS via Model Description A javascript: link in a model description survives sanitisation, becomes an anchor only after sanitising, and then runs when other users view the model.
- Open WebUI has stored XSS in Excel file preview A crafted spreadsheet's HTML preview is inserted into the page without sanitising, so embedded script runs when the user opens the preview.
- parisneo/lollms vulnerable to stored XSS in the social feature Social feed post content is stored without sanitisation and rendered to viewers, so injected script runs in their browsers.
- MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface Unsafe YAML parsing of MLmodel metadata lets an uploaded artifact inject script that runs in another user's browser when viewed in the UI.
- n8n has XSS in its Credential Management Flow A crafted OAuth2 credential with a javascript: URL in the authorization URL field runs script in the browser of a victim who clicks the authorize button.
- n8n has XSS in Chat Trigger Node through Custom CSS Custom CSS in the Chat Trigger node is stored after a misconfigured sanitize-html pass, allowing script to run on the public chat page.
- n8n has a Stored XSS Vulnerability in its Form Trigger A flaw in CSS sanitisation of Form Trigger nodes lets a stored payload run in every visitor's browser of the published form.
- n8n: Authenticated XSS and Open Redirect via Form Node A workflow editor can store HTML in a form description or exploit a loose iframe sandbox, so visitors get script execution or redirects.
- n8n Vulnerable to XSS via Binary Data Inline HTML Rendering Binary data without a filename is served inline on the main origin without download or CSP headers, so crafted HTML runs script in a victim's session.
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in nltk A crafted lookup URL places its word into the WordNet browser page unescaped, so injected markup runs in the local app's origin.
- Flowise has Arbitrary File Upload via MIME Spoofing The unauthenticated upload endpoint trusts the client-supplied Content-Type, so attackers can store active files such as scripts by spoofing an allowed type.
- n8n Vulnerable to Stored XSS via Various Nodes A workflow author embeds script in node-rendered pages such as forms and chat, which then runs for any visitor.
- Pydantic AI has Stored XSS via Path Traversal in Web UI CDN URL An unvalidated version parameter lets traversal sequences make the server fetch attacker-controlled HTML from the CDN and serve it in the app's origin.
- n8n's Improper CSP Enforcement in Webhook Responses May Allow Stored XSS The CSP sandbox is not applied to some webhook and HTTP responses, so an author's HTML runs with the origin's privileges for other users.
- n8n Has Stored Cross-site Scripting via Markdown Rendering in Workflow UI Markdown rendering in workflow sticky notes lets a stored script run in other users' sessions when they open the workflow.
- Label Studio is vulnerable to full account takeover by chaining Stored XSS + IDOR in User Profile via custom_hotkeys field Stored script injected through a hotkey setting runs in other users' browsers, and missing CSRF protection lets it steal API tokens.
- n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox HTML returned by the Respond to Webhook node escapes the iframe sandbox meant to contain it, so injected scripts run in the editor's top-level window.
- Open WebUI Vulnerable to Stored DOM XSS via Note 'Download PDF' SVG markup in imported Markdown is inserted into the PDF export via innerHTML without sanitising, so script runs in the exporting user's session.
- Open WebUI vulnerable to Stored DOM XSS via prompts when 'Insert Prompt as Rich Text' is enabled resulting in ATO/RCE Prompt bodies inserted as rich text are converted to HTML and assigned to innerHTML without sanitisation, so stored markup runs in other users' browsers.
- Flowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panel Chat message content is rendered unsanitised in the admin message viewer, so injected script runs for the admin and can read localStorage.
- Stored XSS in n8n LangChain Chat Trigger Node via initialMessages Parameter A script stored in the initial messages setting runs in the browser of every visitor to the public chat page.
- N8N's Chat Trigger component is vulnerable to XSS The Chat Trigger accepts arbitrary file uploads, including HTML files that execute script when opened in the application's origin.
- Stored XSS in n8n Form Trigger allows Account Takeover via injected iframe and video/source An authenticated user stores HTML in a form trigger using iframe srcdoc or video and source onerror payloads, which run in victims' browsers and steal session tokens.
- label-studio vulnerable to Cross-Site Scripting (Reflected) via the label_config parameter. A crafted label_config posted to the upload-example endpoint is reflected into a response the browser renders, running script in the victim's session.
- n8n Vulnerable to Stored XSS through Attachments View Endpoint The attachment view endpoint lets callers choose the response MIME type, so an uploaded HTML file can be served as text/html and run script.
- one-api Cross-site Scripting vulnerability Homepage content set through system settings is rendered without sanitisation, so injected script runs in visitors' browsers.
- LocalAI Cross-Site Scripting (XSS) vulnerability in its search functionality Search input is not properly sanitised before being rendered, letting injected JavaScript run in a victim's browser.
- AgentScope stored cross-site scripting (XSS) vulnerability A user-controlled run identifier is rendered into the run inspection page as raw HTML, so attacker script runs in viewers' browsers.
- Open WebUI stored cross-site scripting (XSS) vulnerability The model description set through the add model endpoint is stored with insufficient sanitising and later runs as script when rendered in chat.
- Open WebUI Vulnerable to Cross-Site Scripting (XSS) via Chat File Upload An uploaded chat file carries script content that runs in a victim's browser when the file is opened through a link or shared chat.
- Label Studio allows Cross-Site Scripting (XSS) via GET request to `/projects/upload-example` endpoint The GET upload-example endpoint renders HTML from a crafted label_config parameter without sanitisation, so opening the link runs attacker script.
- LocalAI Cross-site Scripting vulnerability Crafted parameters sent to the delete model API store a script that runs in the browser of users who open the homepage.