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.
67609 vulnerabilities reference this CWE, most recent first.
GHSA-66M2-V9V9-95C3
Vulnerability from github – Published: 2026-03-30 16:19 – Updated: 2026-04-27 16:26Summary
Vulnerability: Stored DOM XSS via System Settings – Mail Settings (Same-Page Attribute Breakout & Persistent Payload Injection)
- Stored Cross-Site Scripting via Unsanitized Mail Settings Configuration Fields
Description
The application fails to properly sanitize user-controlled input within System Settings – Mail Settings. Several configuration fields, including Mail Server, Mail Port, Email Address, Email Password, Mail Protocol, and TLS settings, accept attacker-controlled input that is stored server-side and later rendered without proper output encoding.
Unlike public-facing XSS that executes on landing pages, this vulnerability executes immediately on the same settings page. The injected payload breaks out of the HTML attribute context and is interpreted by the browser when rendered, resulting in same-page DOM-based XSS.
This represents different functionality and a separate vulnerability from landing-page injection.
Example Affected Fields
- Mail Server:
test - Mail Port:
465 - Email Address:
simple@gmail.com - Email Password: (any input)
- Mail Protocol:
SMTP - Domain:
simple@domain.com
Affected Functionality
- System Settings – Mail Settings configuration
- Same-page rendering of user-controlled input fields
- DOM attribute injection within form inputs
- Storage and retrieval of mail configuration values
Attack Scenario
- An attacker injects a malicious JavaScript payload into one or more Mail Settings fields.
- The payload breaks out of the HTML attribute context.
- The application stores and re-renders the payload without sanitization or encoding.
- The payload executes immediately on the same settings page.
- The script executes in the browser context of the authenticated user managing Mail Settings.
Impact
- Persistent Stored XSS
- Immediate Same-Page DOM XSS execution
- Execution of arbitrary JavaScript in victims’ browsers
- Administrative privilege escalation
- Full administrator account takeover
- Full account takeover across all roles
- Full compromise of the entire platform
Endpoints:
- /backend/settings/ (Mail Settings)
Steps To Reproduce (POC)
- Navigate to System Settings -> Mail Settings
- Insert the following XSS payload into any Mail Settings field:
test"><img src=1 onerror=alert()>" class="form-control" placeholder="Name" required> - Save the settings
- Observe that the payload breaks out of the input attribute context
- The XSS executes immediately on the same page
Remediation
- Never use .html() or any innerHTML-style sinks for user-controlled input in PHP or JavaScript.
- Apply proper HTML encoding and input sanitization for all configuration fields.
- Enforce CSP, HttpOnly, SameSite, and Secure flags for cookies to reduce the severity of XSS and potential CSRF escalation.
- Audit all other system settings fields for similar attribute injection vulnerabilities.
Ready Video POC:
https://mega.nz/file/KRNhUI6Q#NGC3Bow3RlnmdU1H2bGu1BGbpfIc-awi6IlvTp08V1s
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.28.6.0"
},
"package": {
"ecosystem": "Packagist",
"name": "ci4-cms-erp/ci4ms"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.31.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-27599"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-30T16:19:05Z",
"nvd_published_at": "2026-03-30T21:17:08Z",
"severity": "CRITICAL"
},
"details": "## Summary\n### **Vulnerability: Stored DOM XSS via System Settings \u2013 Mail Settings (Same-Page Attribute Breakout \u0026 Persistent Payload Injection)**\n- Stored Cross-Site Scripting via Unsanitized Mail Settings Configuration Fields\n\n### Description\nThe application fails to properly sanitize user-controlled input within **System Settings \u2013 Mail Settings**. Several configuration fields, including **Mail Server, Mail Port, Email Address, Email Password, Mail Protocol, and TLS settings**, accept attacker-controlled input that is stored server-side and later rendered without proper output encoding.\n\nUnlike public-facing XSS that executes on landing pages, this vulnerability executes immediately on the same settings page. The injected payload breaks out of the HTML attribute context and is interpreted by the browser when rendered, resulting in same-page DOM-based XSS.\n\nThis represents different functionality and a separate vulnerability from landing-page injection.\n\n### Example Affected Fields\n- Mail Server: `test`\n- Mail Port: `465`\n- Email Address: `simple@gmail.com`\n- Email Password: (any input)\n- Mail Protocol: `SMTP`\n- Domain: `simple@domain.com`\n\n### Affected Functionality\n- System Settings \u2013 Mail Settings configuration\n- Same-page rendering of user-controlled input fields\n- DOM attribute injection within form inputs\n- Storage and retrieval of mail configuration values\n\n### Attack Scenario\n- An attacker injects a malicious JavaScript payload into one or more Mail Settings fields.\n- The payload breaks out of the HTML attribute context.\n- The application stores and re-renders the payload without sanitization or encoding.\n- The payload executes immediately on the same settings page.\n- The script executes in the browser context of the authenticated user managing Mail Settings.\n\n### Impact\n- Persistent Stored XSS\n- Immediate Same-Page DOM XSS execution\n- Execution of arbitrary JavaScript in victims\u2019 browsers\n- Administrative privilege escalation\n- Full administrator account takeover\n- Full account takeover across all roles\n- Full compromise of the entire platform\n\nEndpoints:\n- `/backend/settings/` (Mail Settings)\n\n## Steps To Reproduce (POC)\n1. Navigate to System Settings -\u003e Mail Settings\n2. Insert the following XSS payload into any Mail Settings field:\n`test\"\u003e\u003cimg src=1 onerror=alert()\u003e\" class=\"form-control\" placeholder=\"Name\" required\u003e`\n3. Save the settings\n4. Observe that the payload breaks out of the input attribute context\n5. The XSS executes immediately on the same page\n\n## Remediation\n- Never use .html() or any innerHTML-style sinks for user-controlled input in PHP or JavaScript.\n- Apply proper **HTML encoding and input sanitization** for all configuration fields.\n- Enforce CSP, HttpOnly, SameSite, and Secure flags for cookies to reduce the severity of XSS and potential CSRF escalation.\n- Audit all other system settings fields for similar attribute injection vulnerabilities.\n\n# Ready Video POC:\nhttps://mega.nz/file/KRNhUI6Q#NGC3Bow3RlnmdU1H2bGu1BGbpfIc-awi6IlvTp08V1s",
"id": "GHSA-66m2-v9v9-95c3",
"modified": "2026-04-27T16:26:32Z",
"published": "2026-03-30T16:19:05Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/ci4-cms-erp/ci4ms/security/advisories/GHSA-66m2-v9v9-95c3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27599"
},
{
"type": "PACKAGE",
"url": "https://github.com/ci4-cms-erp/ci4ms"
},
{
"type": "WEB",
"url": "https://mega.nz/file/KRNhUI6Q#NGC3Bow3RlnmdU1H2bGu1BGbpfIc-awi6IlvTp08V1s"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "ci4-cms-erp/ci4ms: System Settings (Mail Settings) Full Platform Compromise \u0026 Full Account Takeover for All-Roles \u0026 Privilege-Escalation via Stored DOM XSS"
}
GHSA-66M6-JPMJ-9H43
Vulnerability from github – Published: 2023-08-31 06:30 – Updated: 2024-04-04 07:18The CHP Ads Block Detector plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings reachable though an AJAX action in versions up to, and including, 3.9.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
{
"affected": [],
"aliases": [
"CVE-2023-2354"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-31T06:15:09Z",
"severity": "MODERATE"
},
"details": "The CHP Ads Block Detector plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings reachable though an AJAX action in versions up to, and including, 3.9.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.",
"id": "GHSA-66m6-jpmj-9h43",
"modified": "2024-04-04T07:18:33Z",
"published": "2023-08-31T06:30:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-2354"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/2920522/chp-ads-block-detector"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/2922313/chp-ads-block-detector"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/2926660/chp-ads-block-detector"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/6f8514c9-0e11-4e26-ba0b-1d08a990b56c?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-66M7-9P59-W5RM
Vulnerability from github – Published: 2025-12-10 21:31 – Updated: 2025-12-10 21:31Adobe Experience Manager versions 6.5.23 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that could be exploited by a low privileged attacker to execute malicious scripts in the context of the victim's browser. Exploitation of this issue requires user interaction, such as visiting a crafted URL or interacting with a manipulated web page.
{
"affected": [],
"aliases": [
"CVE-2025-64583"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-10T19:16:21Z",
"severity": "MODERATE"
},
"details": "Adobe Experience Manager versions 6.5.23 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that could be exploited by a low privileged attacker to execute malicious scripts in the context of the victim\u0027s browser. Exploitation of this issue requires user interaction, such as visiting a crafted URL or interacting with a manipulated web page.",
"id": "GHSA-66m7-9p59-w5rm",
"modified": "2025-12-10T21:31:35Z",
"published": "2025-12-10T21:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64583"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/experience-manager/apsb25-115.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-66MG-WFXJ-X3XV
Vulnerability from github – Published: 2023-04-20 12:30 – Updated: 2024-04-04 03:36The Snyk Advisor website (https://snyk.io/advisor/) was vulnerable to a stored XSS prior to 28th March 2023. A feature of Snyk Advisor is to display the contents of a scanned package's Readme on its package health page. An attacker could create a package in NPM with an associated markdown README file containing XSS-able HTML tags. Upon Snyk Advisor importing the package, the XSS would run each time an end user browsed to the package's page on Snyk Advisor.
{
"affected": [],
"aliases": [
"CVE-2023-1767"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-04-20T10:15:07Z",
"severity": "MODERATE"
},
"details": "The Snyk Advisor website (https://snyk.io/advisor/) was vulnerable to a stored XSS prior to 28th March 2023. A feature of Snyk Advisor is to display the contents of a scanned package\u0027s Readme on its package health page. An attacker could create a package in NPM with an associated markdown README file containing XSS-able HTML tags. Upon Snyk Advisor importing the package, the XSS would run each time an end user browsed to the package\u0027s page on Snyk Advisor.",
"id": "GHSA-66mg-wfxj-x3xv",
"modified": "2024-04-04T03:36:41Z",
"published": "2023-04-20T12:30:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1767"
},
{
"type": "WEB",
"url": "https://support.snyk.io/hc/en-us/articles/10146704933405"
},
{
"type": "WEB",
"url": "https://weizman.github.io/2023/04/10/snyk-xss"
}
],
"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"
}
]
}
GHSA-66P2-MGHC-64Q3
Vulnerability from github – Published: 2022-05-24 21:59 – Updated: 2023-01-24 21:30XSS was discovered in CentOS-WebPanel.com (aka CWP) CentOS Web Panel through 0.9.8.747 via the testacc/fileManager2.php fm_current_dir or filename parameter.
{
"affected": [],
"aliases": [
"CVE-2019-12190"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-05-21T18:29:00Z",
"severity": "MODERATE"
},
"details": "XSS was discovered in CentOS-WebPanel.com (aka CWP) CentOS Web Panel through 0.9.8.747 via the testacc/fileManager2.php fm_current_dir or filename parameter.",
"id": "GHSA-66p2-mghc-64q3",
"modified": "2023-01-24T21:30:32Z",
"published": "2022-05-24T21:59:53Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-12190"
},
{
"type": "WEB",
"url": "https://github.com/tuyenhva/CVE-2019-12190"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-66P5-MMJ3-2QRW
Vulnerability from github – Published: 2022-05-17 02:10 – Updated: 2022-05-17 02:10Cross-site scripting (XSS) vulnerability in phpcksec.php in Stefan Ott phpcksec 0.2 allows remote attackers to inject arbitrary web script or HTML via the path parameter.
{
"affected": [],
"aliases": [
"CVE-2008-6609"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-04-06T16:30:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in phpcksec.php in Stefan Ott phpcksec 0.2 allows remote attackers to inject arbitrary web script or HTML via the path parameter.",
"id": "GHSA-66p5-mmj3-2qrw",
"modified": "2022-05-17T02:10:54Z",
"published": "2022-05-17T02:10:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-6609"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/47425"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.org/0812-exploits/phpcksec-xssdisclose.txt"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/32890"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-66PP-6WXC-WM33
Vulnerability from github – Published: 2024-02-12 06:30 – Updated: 2026-04-28 21:33Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Prasidhda Malla Honeypot for WP Comment allows Reflected XSS.This issue affects Honeypot for WP Comment: from n/a through 2.2.3.
{
"affected": [],
"aliases": [
"CVE-2024-24933"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-12T06:15:09Z",
"severity": "HIGH"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in Prasidhda Malla Honeypot for WP Comment allows Reflected XSS.This issue affects Honeypot for WP Comment: from n/a through 2.2.3.",
"id": "GHSA-66pp-6wxc-wm33",
"modified": "2026-04-28T21:33:58Z",
"published": "2024-02-12T06:30:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-24933"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/honeypot-for-wp-comment/wordpress-honeypot-for-wp-comment-plugin-2-2-3-reflected-cross-site-scripting-xss-vulnerability?_s_id=cve"
}
],
"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:L",
"type": "CVSS_V3"
}
]
}
GHSA-66Q2-C4X8-8X2C
Vulnerability from github – Published: 2025-03-13 06:30 – Updated: 2025-03-14 18:30The WoWPth WordPress plugin through 2.0 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin
{
"affected": [],
"aliases": [
"CVE-2025-1486"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-13T06:15:37Z",
"severity": "HIGH"
},
"details": "The WoWPth WordPress plugin through 2.0 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin",
"id": "GHSA-66q2-c4x8-8x2c",
"modified": "2025-03-14T18:30:49Z",
"published": "2025-03-13T06:30:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1486"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/182ecda8-3385-4f9f-a917-efdeb237247c"
}
],
"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:L",
"type": "CVSS_V3"
}
]
}
GHSA-66Q5-CJ5G-WRFX
Vulnerability from github – Published: 2026-06-04 18:56 – Updated: 2026-06-04 18:56Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section
Summary
A stored Cross-Site Scripting vulnerability (CWE-79; chained CWE-829, Inclusion of Functionality from Untrusted Control Sphere) in the AVideo YouTubeAPI plugin renders the snippet.title field returned by the YouTube Data API into the homepage gallery markup with no HTML encoding. The title is set by the YouTube video uploader (anyone in the world) and is treated by AVideo as trusted content. A YouTube uploader who controls a video matching the operator's configured query injects HTML into the AVideo homepage by setting their video's title to a JavaScript-bearing string; the payload then executes in the browser of every visitor who loads any page that renders the gallery.
Details
plugin/YouTubeAPI/YouTubeAPI.php::listVideos() fetches search results from the YouTube Data API and stores the snippet.title field unchanged inside a YPTvideoObject:
// plugin/YouTubeAPI/YouTubeAPI.php (listVideos excerpt)
$searchResponse = $youtube->search->listSearch(
'snippet,contentDetails,statistics', $options
);
foreach ($searchResponse['items'] as $searchResult) {
$vid = new YPTvideoObject(
$searchResult["id"]["videoId"],
$searchResult['snippet']["title"], // uploader-controlled
$searchResult['snippet']["description"],
$searchResult['snippet']["thumbnails"]["high"]["url"],
$searchResult['snippet']["channelTitle"],
"https://www.youtube.com/embed/{$searchResult['id']['videoId']}"
);
$object->videos[] = $vid;
}
plugin/YouTubeAPI/gallerySection.php then renders the title into three HTML contexts inside each gallery card. Four reflection sites total, three of them completely unprotected:
// plugin/YouTubeAPI/gallerySection.php (foreach body)
$youtubeTitle = $video->title;
...
<a class="evideo" href="<?php echo $youtubeEmbedLink; ?>" title="<?php echo $youtubeTitle; ?>"> <!-- (i) attribute -->
<img src="<?php echo $youtubeThumbs; ?>" alt="<?php echo str_replace('"', '', $youtubeTitle); ?>" ... /> <!-- (ii) attribute, partial -->
</a>
<a class="h6 evideo" href="<?php echo $youtubeEmbedLink; ?>" title="<?php echo $youtubeTitle; ?>"> <!-- (iii) attribute -->
<h2><?php echo $youtubeTitle; ?></h2> <!-- (iv) element body -->
</a>
Sites (i), (iii), and (iv) call no encoder. Site (ii) applies str_replace('"', '', $youtubeTitle) which strips quotes from one attribute and leaves the other three reflections untouched. The strongest sink is (iv) at line 60: a title containing <script>alert(2222)</script> produces <h2><script>alert(2222)</script></h2> in the rendered DOM, which the browser parses as a live script element and executes synchronously. The single half-mitigation at line 57 is the maintainer's evidence of awareness of the attribute-injection risk; the same developer left the other three sinks unprotected.
AVideo additionally caches the YouTube response for cacheTimeout seconds (default 3600), so even after the title is changed on YouTube or the video is removed, the AVideo gallery continues to serve the malicious title until the cache expires or is manually flushed.
Affected product: AVideo (WWBN), YouTubeAPI plugin Tested version: master branch, commit 122b184 (snapshot dated 2026-05-22)
PoC
The AVideo operator must have the YouTubeAPI plugin enabled (the default after configuring a YouTube Data API key) with showGallerySection=true (the default). The attacker controls a YouTube video (uploaded under any free YouTube account) whose title is set to:
<script>alert(2222)</script>
The attacker arranges for the AVideo operator's configured YouTube search query (the keyword plugin setting, typically a channel name or topical phrase) to match the hostile video. The matching condition is the same as a normal YouTube search: a unique phrase in the video's description, a channel name the operator follows, or any query the operator has configured.
After AVideo's cacheTimeout window elapses (default 3600 seconds) and a fresh listVideos() call fetches the malicious title, any visitor opening the AVideo homepage triggers an alert(2222) modal dialog as the gallery card renders.
For deterministic test reproduction, deploy a mock YouTube Data API service that impersonates www.googleapis.com and youtube.googleapis.com on the AVideo Docker network and returns the malicious title directly. The PoC then reduces to:
https://avideo.example/
Configure the YouTubeAPI plugin in the admin panel (/plugins) with any non-empty developer_key and any keyword value, then load the homepage. The browser fires alert(2222) as the gallery section finishes rendering.
Impact
This is a Stored XSS vulnerability (CWE-79) in a publicly-rendered HTML context, with the data source under attacker control (CWE-829). Every visitor who loads any AVideo page rendering the YouTubeAPI gallery section is impacted: the injected JavaScript runs in the visitor's session under the AVideo origin, reads non-HttpOnly cookies, and issues authenticated requests as the visitor. When the visitor is an AVideo administrator, the injected JavaScript performs any admin action (create user, promote to admin, change configuration, install plugin) that uses cookie-based authentication without an additional CSRF token, escalating the bug into full administrative takeover. The payload persists for the duration of cacheTimeout (default 3600 seconds) after the malicious title is set on YouTube and survives YouTube removing the hostile video for the same window.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "WWBN/AVideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "29.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-50183"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-04T18:56:53Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "# Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section\n\n## Summary\n\nA stored Cross-Site Scripting vulnerability (CWE-79; chained CWE-829, Inclusion of Functionality from Untrusted Control Sphere) in the AVideo YouTubeAPI plugin renders the `snippet.title` field returned by the YouTube Data API into the homepage gallery markup with no HTML encoding. The title is set by the YouTube video uploader (anyone in the world) and is treated by AVideo as trusted content. A YouTube uploader who controls a video matching the operator\u0027s configured query injects HTML into the AVideo homepage by setting their video\u0027s title to a JavaScript-bearing string; the payload then executes in the browser of every visitor who loads any page that renders the gallery.\n\n## Details\n\n`plugin/YouTubeAPI/YouTubeAPI.php::listVideos()` fetches search results from the YouTube Data API and stores the `snippet.title` field unchanged inside a `YPTvideoObject`:\n\n```php\n// plugin/YouTubeAPI/YouTubeAPI.php (listVideos excerpt)\n$searchResponse = $youtube-\u003esearch-\u003elistSearch(\n \u0027snippet,contentDetails,statistics\u0027, $options\n);\nforeach ($searchResponse[\u0027items\u0027] as $searchResult) {\n $vid = new YPTvideoObject(\n $searchResult[\"id\"][\"videoId\"],\n $searchResult[\u0027snippet\u0027][\"title\"], // uploader-controlled\n $searchResult[\u0027snippet\u0027][\"description\"],\n $searchResult[\u0027snippet\u0027][\"thumbnails\"][\"high\"][\"url\"],\n $searchResult[\u0027snippet\u0027][\"channelTitle\"],\n \"https://www.youtube.com/embed/{$searchResult[\u0027id\u0027][\u0027videoId\u0027]}\"\n );\n $object-\u003evideos[] = $vid;\n}\n```\n\n`plugin/YouTubeAPI/gallerySection.php` then renders the title into three HTML contexts inside each gallery card. Four reflection sites total, three of them completely unprotected:\n\n```php\n// plugin/YouTubeAPI/gallerySection.php (foreach body)\n$youtubeTitle = $video-\u003etitle;\n...\n\u003ca class=\"evideo\" href=\"\u003c?php echo $youtubeEmbedLink; ?\u003e\" title=\"\u003c?php echo $youtubeTitle; ?\u003e\"\u003e \u003c!-- (i) attribute --\u003e\n \u003cimg src=\"\u003c?php echo $youtubeThumbs; ?\u003e\" alt=\"\u003c?php echo str_replace(\u0027\"\u0027, \u0027\u0027, $youtubeTitle); ?\u003e\" ... /\u003e \u003c!-- (ii) attribute, partial --\u003e\n\u003c/a\u003e\n\u003ca class=\"h6 evideo\" href=\"\u003c?php echo $youtubeEmbedLink; ?\u003e\" title=\"\u003c?php echo $youtubeTitle; ?\u003e\"\u003e \u003c!-- (iii) attribute --\u003e\n \u003ch2\u003e\u003c?php echo $youtubeTitle; ?\u003e\u003c/h2\u003e \u003c!-- (iv) element body --\u003e\n\u003c/a\u003e\n```\n\nSites (i), (iii), and (iv) call no encoder. Site (ii) applies `str_replace(\u0027\"\u0027, \u0027\u0027, $youtubeTitle)` which strips quotes from one attribute and leaves the other three reflections untouched. The strongest sink is (iv) at line 60: a title containing `\u003cscript\u003ealert(2222)\u003c/script\u003e` produces `\u003ch2\u003e\u003cscript\u003ealert(2222)\u003c/script\u003e\u003c/h2\u003e` in the rendered DOM, which the browser parses as a live script element and executes synchronously. The single half-mitigation at line 57 is the maintainer\u0027s evidence of awareness of the attribute-injection risk; the same developer left the other three sinks unprotected.\n\nAVideo additionally caches the YouTube response for `cacheTimeout` seconds (default 3600), so even after the title is changed on YouTube or the video is removed, the AVideo gallery continues to serve the malicious title until the cache expires or is manually flushed.\n\n**Affected product:** AVideo (WWBN), YouTubeAPI plugin\n**Tested version:** master branch, commit 122b184 (snapshot dated 2026-05-22)\n\n## PoC\n\nThe AVideo operator must have the YouTubeAPI plugin enabled (the default after configuring a YouTube Data API key) with `showGallerySection=true` (the default). The attacker controls a YouTube video (uploaded under any free YouTube account) whose title is set to:\n\n```\n\u003cscript\u003ealert(2222)\u003c/script\u003e\n```\n\nThe attacker arranges for the AVideo operator\u0027s configured YouTube search query (the `keyword` plugin setting, typically a channel name or topical phrase) to match the hostile video. The matching condition is the same as a normal YouTube search: a unique phrase in the video\u0027s description, a channel name the operator follows, or any query the operator has configured.\n\nAfter AVideo\u0027s `cacheTimeout` window elapses (default 3600 seconds) and a fresh `listVideos()` call fetches the malicious title, any visitor opening the AVideo homepage triggers an `alert(2222)` modal dialog as the gallery card renders.\n\nFor deterministic test reproduction, deploy a mock YouTube Data API service that impersonates `www.googleapis.com` and `youtube.googleapis.com` on the AVideo Docker network and returns the malicious title directly. The PoC then reduces to:\n\n```\nhttps://avideo.example/\n```\n\nConfigure the YouTubeAPI plugin in the admin panel (`/plugins`) with any non-empty `developer_key` and any `keyword` value, then load the homepage. The browser fires `alert(2222)` as the gallery section finishes rendering.\n\n## Impact\n\nThis is a Stored XSS vulnerability (CWE-79) in a publicly-rendered HTML context, with the data source under attacker control (CWE-829). Every visitor who loads any AVideo page rendering the YouTubeAPI gallery section is impacted: the injected JavaScript runs in the visitor\u0027s session under the AVideo origin, reads non-`HttpOnly` cookies, and issues authenticated requests as the visitor. When the visitor is an AVideo administrator, the injected JavaScript performs any admin action (create user, promote to admin, change configuration, install plugin) that uses cookie-based authentication without an additional CSRF token, escalating the bug into full administrative takeover. The payload persists for the duration of `cacheTimeout` (default 3600 seconds) after the malicious title is set on YouTube and survives YouTube removing the hostile video for the same window.",
"id": "GHSA-66q5-cj5g-wrfx",
"modified": "2026-06-04T18:56:53Z",
"published": "2026-06-04T18:56:53Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-66q5-cj5g-wrfx"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/7292129eaee5f609beae103b5cb387d55f17b877"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
}
],
"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:N",
"type": "CVSS_V3"
}
],
"summary": "WWBN AVideo: Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section"
}
GHSA-66Q6-9VJF-C735
Vulnerability from github – Published: 2023-01-20 21:30 – Updated: 2023-01-25 21:30Cross site scripting (XSS) vulnerability in Hundredrabbits Left 7.1.5 for MacOS allows attackers to execute arbitrary code via the meta tag.
{
"affected": [],
"aliases": [
"CVE-2022-45558"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-01-20T19:15:00Z",
"severity": "MODERATE"
},
"details": "Cross site scripting (XSS) vulnerability in Hundredrabbits Left 7.1.5 for MacOS allows attackers to execute arbitrary code via the meta tag.",
"id": "GHSA-66q6-9vjf-c735",
"modified": "2023-01-25T21:30:19Z",
"published": "2023-01-20T21:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-45558"
},
{
"type": "WEB",
"url": "https://github.com/hundredrabbits/Left/issues/168"
}
],
"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"
}
]
}
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.