Browse / AI Framework and Platform Flaws / Cross-site scripting
Cross-site scripting
68 records in AI Framework and Platform Flaws.
- Lollms vulnerable to Cross-site Scripting The SVG sanitiser removes only script tags and on-event attributes, so other SVG vectors survive and run script when a victim opens the file.
- Gradio has an XSS on every Gradio server via upload of HTML files, JS files, or SVG files Users who upload HTML, JavaScript or SVG files to Gradio can have scripts run in other users' browsers when those files are viewed.
- Flowise and Flowise Chat Embed vulnerable to Stored Cross-site Scripting The chat embed does not sanitise stored input, so injected script runs in viewers' browsers when messages are displayed.
- MindsDB Cross-site Scripting vulnerability Script stored in engine, database, project or dataset names runs in the browser of any user who lists them in the web UI.
- Khoj Vulnerable to Stored Cross-site Scripting In Automate (Preview feature) The automation instruction parameter is rendered into the config page without escaping, so injected HTML and script run in viewers' browsers.
- Flowise Cross-site Scripting in api/v1/chatflows/id An unknown chatflow ID is echoed unescaped into an HTML 404 page, so a crafted URL runs script in the victim's browser.
- Flowise Cross-site Scripting in /api/v1/chatflows-streaming/id An unknown chatflow ID is echoed unescaped into a text/html 404 page, letting a crafted URL inject script.
- Flowise Cross-site Scripting in /api/v1/public-chatflows/id The 404 page reflects the unvalidated chatflow ID as text/html, so injected script runs in users' sessions.
- Flowise Cross-site Scripting in/api/v1/credentials/id An unknown ID is reflected unescaped into a text/html 404 page, letting attacker-supplied script run in a victim's session.
- Reflected Cross-Site Scripting (XSS) in zenml An unvalidated redirect parameter is reflected into the survey page, letting a crafted link run script in a victim's session.
- Cross site scripting in zenml A stored script payload placed in the logo URL field runs in other users' browsers when the page renders it.
- Arbitrary JavaScript execution due to using outdated libraries A crafted PDF embeds script in font data that an outdated pdf.js build executes in the viewer when the app renders it.
- Cross-site Scripting (XSS) in mindsdb/mindsdb A CSV uploaded with embedded JavaScript is rendered without escaping when viewed, so the script runs in the viewer's browser.
- MLFlow Cross-site Scripting vulnerability leads to client-side Remote Code Execution Dataset table fields are rendered without sanitization, so an untrusted dataset injects script into the notebook view and runs code on the client.
- Label Studio vulnerable to Cross-site Scripting if `<Choices>` or `<Labels>` are used in labeling config Imported task data is rendered unsanitised inside Choices or Labels tags, so an embedded image handler runs script in other users' browsers.
- Cross-site Scripting Vulnerability on Data Import Remote import saves downloaded content under a URL-derived name, so an attacker-hosted HTML file runs script when viewed on the site.
- Cross-site Scripting Vulnerability on Avatar Upload Avatar upload only checks that a file parses as an image, so a crafted file containing HTML is served and rendered, running script in the site origin.
- Cross-site Scripting (XSS) in MLflow The Content-Type request header is echoed into an HTML response without escaping, so a crafted header runs script in the victim's browser.