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.
68581 vulnerabilities reference this CWE, most recent first.
GHSA-73QV-XHR2-28JM
Vulnerability from github – Published: 2022-05-02 03:40 – Updated: 2025-04-09 04:14Cross-site scripting (XSS) vulnerability in Xapian Omega before 1.0.16 allows remote attackers to inject arbitrary web script or HTML via unspecified CGI parameter values, which are sometimes included in exception messages.
{
"affected": [],
"aliases": [
"CVE-2009-2947"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-09-14T16:30:00Z",
"severity": "MODERATE"
},
"details": "Cross-site scripting (XSS) vulnerability in Xapian Omega before 1.0.16 allows remote attackers to inject arbitrary web script or HTML via unspecified CGI parameter values, which are sometimes included in exception messages.",
"id": "GHSA-73qv-xhr2-28jm",
"modified": "2025-04-09T04:14:24Z",
"published": "2022-05-02T03:40:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-2947"
},
{
"type": "WEB",
"url": "http://lists.xapian.org/pipermail/xapian-discuss/2009-September/007115.html"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/36674"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/36693"
},
{
"type": "WEB",
"url": "http://svn.xapian.org/%2Acheckout%2A/tags/1.0.16/xapian-applications/omega/NEWS"
},
{
"type": "WEB",
"url": "http://svn.xapian.org/*checkout*/tags/1.0.16/xapian-applications/omega/NEWS"
},
{
"type": "WEB",
"url": "http://www.debian.org/security/2009/dsa-1882"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/36317"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-73QW-564R-5FF3
Vulnerability from github – Published: 2023-03-17 15:30 – Updated: 2023-03-23 15:30Stored Cross-Site Scripting (XSS) vulnerability in John West Slideshow SE plugin <= 2.5.5 versions.
{
"affected": [],
"aliases": [
"CVE-2022-43461"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-03-17T14:15:00Z",
"severity": "MODERATE"
},
"details": "Stored Cross-Site Scripting (XSS) vulnerability in John West Slideshow SE plugin \u003c= 2.5.5 versions.",
"id": "GHSA-73qw-564r-5ff3",
"modified": "2023-03-23T15:30:28Z",
"published": "2023-03-17T15:30:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-43461"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/slideshow-se/wordpress-slideshow-se-plugin-2-5-5-auth-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:N",
"type": "CVSS_V3"
}
]
}
GHSA-73R6-JQF2-WH3H
Vulnerability from github – Published: 2022-03-08 00:00 – Updated: 2022-03-17 00:02The CP Blocks WordPress plugin before 1.0.15 does not sanitise and escape its "License ID" settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html is disallowed.
{
"affected": [],
"aliases": [
"CVE-2022-0448"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-03-07T09:15:00Z",
"severity": "MODERATE"
},
"details": "The CP Blocks WordPress plugin before 1.0.15 does not sanitise and escape its \"License ID\" settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html is disallowed.",
"id": "GHSA-73r6-jqf2-wh3h",
"modified": "2022-03-17T00:02:55Z",
"published": "2022-03-08T00:00:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-0448"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/d4ff63ee-28e6-486e-9aa7-c878b97f707c"
}
],
"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-73R7-6QF7-8658
Vulnerability from github – Published: 2025-05-23 15:31 – Updated: 2026-04-01 18:35Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in GoodLayers Goodlayers Hotel allows Reflected XSS. This issue affects Goodlayers Hotel: from n/a through 3.1.4.
{
"affected": [],
"aliases": [
"CVE-2025-39505"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-05-23T13:15:32Z",
"severity": "HIGH"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in GoodLayers Goodlayers Hotel allows Reflected XSS. This issue affects Goodlayers Hotel: from n/a through 3.1.4.",
"id": "GHSA-73r7-6qf7-8658",
"modified": "2026-04-01T18:35:14Z",
"published": "2025-05-23T15:31:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39505"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/gdlr-hotel/vulnerability/wordpress-goodlayers-hotel-plugin-3-1-4-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-73RF-M3Q4-JPQ4
Vulnerability from github – Published: 2022-05-17 00:30 – Updated: 2022-05-17 00:30IBM Content Navigator & CMIS 2.0.3, 3.0.0, and 3.0.1 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 129832.
{
"affected": [],
"aliases": [
"CVE-2017-1522"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-10-05T17:29:00Z",
"severity": "MODERATE"
},
"details": "IBM Content Navigator \u0026 CMIS 2.0.3, 3.0.0, and 3.0.1 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 129832.",
"id": "GHSA-73rf-m3q4-jpq4",
"modified": "2022-05-17T00:30:20Z",
"published": "2022-05-17T00:30:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-1522"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/129832"
},
{
"type": "WEB",
"url": "http://www.ibm.com/support/docview.wss?uid=swg22008162"
}
],
"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-73RG-F94J-XVHX
Vulnerability from github – Published: 2024-09-20 14:41 – Updated: 2024-09-20 22:07Impact
One longstanding feature of Plate is the ability to add custom DOM attributes to any element or leaf using the attributes property. These attributes are passed to the node component using the nodeProps prop.
Note: The attributes prop that is typically rendered alongside nodeProps is unrelated.
[{
type: 'p',
attributes: { 'data-my-attribute': 'This will be rendered on the paragraph element' },
children: [{
bold: true,
attributes: { 'data-my-attribute': 'This will be rendered on the bold leaf element' },
text: 'Bold text',
}],
}]
const ParagraphElement = ({ attributes, nodeProps, children }) => (
<p
{...attributes}
{...nodeProps} // Arbitrary DOM attributes are injected here
>
{children}
</p>
);
const BoldLeaf = ({ attributes, nodeProps, children }) => (
<strong
{...attributes}
{...nodeProps} // Arbitrary DOM attributes are injected here
>
{children}
</strong>
);
It has come to our attention that this feature can be used for malicious purposes, including cross-site scripting (XSS) and information exposure (specifically, users' IP addresses and whether or not they have opened a malicious document).
Note that the risk of information exposure via attributes is only relevant to applications in which web requests to arbitrary URLs are not ordinarily allowed. Plate editors that allow users to embed images from arbitrary URLs, for example, already carry the risk of leaking users' IP addresses to third parties.
All Plate editors using an affected version of @udecode/plate-core are vulnerable to these information exposure attacks via the style attribute and other attributes that can cause web requests to be sent.
In addition, whether or not a Plate editor is vulnerable to cross-site scripting attacks using attributes depends on a number of factors. The most likely DOM attributes to be vulnerable are href and src on links and iframes respectively. Any component that spreads {...nodeProps} onto an <a> or <iframe> element and does not later override href or src will be vulnerable to XSS.
<a
href={sanitizedHref}
{...attributes}
{...nodeProps} // Definitely vulnerable to XSS since `href` can be overridden
>
<a
{...attributes}
{...nodeProps} // Probably not vulnerable to XSS via `href`
href={sanitizedHref}
>
<a
{...attributes}
{...nodeProps} // May be vulnerable to XSS via `href` if `href` is sometimes omitted from `sanitizedLinkProps`
{...sanitizedLinkProps}
>
React does not allow passing a string to event handler props like onClick, so these are unlikely (but not impossible) to be vulnerable.
The attack surface is larger for users running older browsers, which may be vulnerable to XSS in DOM attributes that are less dangerous (although still vulnerable to information exposure) in modern browsers such as style or background.
Potential attack vectors for delivering malicious Slate content to users include:
- Opening a malicious document stored on the server
- Pasting a malicious Slate fragment into a document
- Receiving malicious Slate operations on a collaborative document
Patches
In patched versions of Plate, we have disabled element.attributes and leaf.attributes for most attribute names by default, with some exceptions including target, alt, width, height, colspan and rowspan on the link, image, video, table cell and table header cell plugins.
If this is a breaking change for you, you can selectively re-enable attributes for certain plugins as follows. Please carefully research and assess the security implications of any attribute you allow, as even seemingly innocuous attributes such as style can be used maliciously.
Plate >= 37
For custom plugins, specify the list of allowed attribute names in the node.dangerouslyAllowAttributes plugin configuration option.
const ImagePlugin = createPlatePlugin({
key: 'image',
node: {
isElement: true,
isVoid: true,
dangerouslyAllowAttributes: ['alt'],
},
});
To modify an existing plugin, use the extend method.
const MyImagePlugin = ImagePlugin.extend({
node: {
dangerouslyAllowAttributes: ['alt'],
},
});
Plate < 37
Note that the patch has been backported to versions @udecode/plate-core@21.5.1 and @udecode/plate-core@36.5.9 only.
For custom plugins, specify the list of allowed attribute names in the dangerouslyAllowAttributes plugin configuration option.
const createImagePlugin = createPluginFactory({
key: 'image',
isElement: true,
isVoid: true,
dangerouslyAllowAttributes: ['alt'],
});
To modify an existing plugin, pass dangerouslyAllowAttributes to the plugin factory.
createImagePlugin({
dangerouslyAllowAttributes: ['alt'],
});
Workarounds
If you are unable to upgrade to any of the patched versions, you should use a tool like patch-package or yarn patch to remove the logic from @udecode/plate-core that adds attributes to nodeProps.
This logic can be found in the getRenderNodeProps function and looks something like this. The entire if statment can safely be removed.
if (!newProps.nodeProps && attributes) {
newProps.nodeProps = attributes;
}
After applying the patch, be sure to test its effectiveness by rendering a Slate value containing an attributes property on some element.
[{
type: 'p',
attributes: { 'data-vulnerable': true },
children: [{ text: 'My paragraph' }],
}]
If the patch was successful, the data-vulnerable="true" attribute should not be present on any DOM element when the Plate editor is rendered in the browser.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@udecode/plate-core"
},
"ranges": [
{
"events": [
{
"introduced": "37.0.0"
},
{
"fixed": "38.0.6"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "@udecode/plate-core"
},
"ranges": [
{
"events": [
{
"introduced": "22.0.0"
},
{
"fixed": "36.5.9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "@udecode/plate-core"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "21.5.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-47061"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2024-09-20T14:41:02Z",
"nvd_published_at": "2024-09-20T19:15:16Z",
"severity": "HIGH"
},
"details": "### Impact\nOne longstanding feature of Plate is the ability to add custom DOM attributes to any element or leaf using the `attributes` property. These attributes are passed to the node component using the `nodeProps` prop.\n\nNote: The `attributes` prop that is typically rendered alongside `nodeProps` is unrelated.\n\n```ts\n[{\n type: \u0027p\u0027,\n attributes: { \u0027data-my-attribute\u0027: \u0027This will be rendered on the paragraph element\u0027 },\n children: [{\n bold: true,\n attributes: { \u0027data-my-attribute\u0027: \u0027This will be rendered on the bold leaf element\u0027 },\n text: \u0027Bold text\u0027,\n }],\n}]\n```\n\n```tsx\nconst ParagraphElement = ({ attributes, nodeProps, children }) =\u003e (\n \u003cp\n {...attributes}\n {...nodeProps} // Arbitrary DOM attributes are injected here\n \u003e\n {children}\n \u003c/p\u003e\n);\n\nconst BoldLeaf = ({ attributes, nodeProps, children }) =\u003e (\n \u003cstrong\n {...attributes}\n {...nodeProps} // Arbitrary DOM attributes are injected here\n \u003e\n {children}\n \u003c/strong\u003e\n);\n```\n\nIt has come to our attention that this feature can be used for malicious purposes, including cross-site scripting (XSS) and information exposure (specifically, users\u0027 IP addresses and whether or not they have opened a malicious document).\n\nNote that the risk of information exposure via `attributes` is only relevant to applications in which web requests to arbitrary URLs are not ordinarily allowed. Plate editors that allow users to embed images from arbitrary URLs, for example, already carry the risk of leaking users\u0027 IP addresses to third parties.\n\nAll Plate editors using an affected version of `@udecode/plate-core` are vulnerable to these information exposure attacks via the `style` attribute and other attributes that can cause web requests to be sent. \n\nIn addition, whether or not a Plate editor is vulnerable to cross-site scripting attacks using `attributes` depends on a number of factors. The most likely DOM attributes to be vulnerable are `href` and `src` on links and iframes respectively. Any component that spreads `{...nodeProps}` onto an `\u003ca\u003e` or `\u003ciframe\u003e` element and does not later override `href` or `src` will be vulnerable to XSS.\n\n```tsx\n\u003ca\n href={sanitizedHref}\n {...attributes}\n {...nodeProps} // Definitely vulnerable to XSS since `href` can be overridden\n\u003e\n```\n\n```tsx\n\u003ca\n {...attributes}\n {...nodeProps} // Probably not vulnerable to XSS via `href`\n href={sanitizedHref}\n\u003e\n```\n\n```tsx\n\u003ca\n {...attributes}\n {...nodeProps} // May be vulnerable to XSS via `href` if `href` is sometimes omitted from `sanitizedLinkProps`\n {...sanitizedLinkProps}\n\u003e\n```\n\nReact does not allow passing a string to event handler props like `onClick`, so these are unlikely (but not impossible) to be vulnerable.\n\nThe attack surface is larger for users running older browsers, which may be vulnerable to XSS in DOM attributes that are less dangerous (although still vulnerable to information exposure) in modern browsers such as `style` or `background`.\n\nPotential attack vectors for delivering malicious Slate content to users include:\n\n- Opening a malicious document stored on the server\n- Pasting a malicious Slate fragment into a document\n- Receiving malicious Slate operations on a collaborative document\n\n### Patches\nIn patched versions of Plate, we have disabled `element.attributes` and `leaf.attributes` for most attribute names by default, with some exceptions including `target`, `alt`, `width`, `height`, `colspan` and `rowspan` on the link, image, video, table cell and table header cell plugins.\n\nIf this is a breaking change for you, you can selectively re-enable `attributes` for certain plugins as follows. Please carefully research and assess the security implications of any attribute you allow, as even seemingly innocuous attributes such as `style` can be used maliciously.\n\n#### Plate \u003e= 37\n\nFor custom plugins, specify the list of allowed attribute names in the `node.dangerouslyAllowAttributes` plugin configuration option.\n\n```ts\nconst ImagePlugin = createPlatePlugin({\n key: \u0027image\u0027,\n node: {\n isElement: true,\n isVoid: true,\n dangerouslyAllowAttributes: [\u0027alt\u0027],\n },\n});\n```\n\nTo modify an existing plugin, use the `extend` method.\n\n```ts\nconst MyImagePlugin = ImagePlugin.extend({\n node: {\n dangerouslyAllowAttributes: [\u0027alt\u0027],\n },\n});\n```\n\n#### Plate \u003c 37\n\nNote that the patch has been backported to versions `@udecode/plate-core@21.5.1` and `@udecode/plate-core@36.5.9` only.\n\nFor custom plugins, specify the list of allowed attribute names in the `dangerouslyAllowAttributes` plugin configuration option.\n\n```ts\nconst createImagePlugin = createPluginFactory({\n key: \u0027image\u0027,\n isElement: true,\n isVoid: true,\n dangerouslyAllowAttributes: [\u0027alt\u0027],\n});\n```\n\nTo modify an existing plugin, pass `dangerouslyAllowAttributes` to the plugin factory.\n\n```ts\ncreateImagePlugin({\n dangerouslyAllowAttributes: [\u0027alt\u0027],\n});\n```\n\n### Workarounds\n\nIf you are unable to upgrade to any of the patched versions, you should use a tool like [`patch-package`](https://www.npmjs.com/package/patch-package) or [`yarn patch`](https://yarnpkg.com/cli/patch) to remove the logic from `@udecode/plate-core` that adds `attributes` to `nodeProps`.\n\nThis logic can be found in the `getRenderNodeProps` function and looks something like this. The entire `if` statment can safely be removed.\n\n```ts\n if (!newProps.nodeProps \u0026\u0026 attributes) {\n newProps.nodeProps = attributes;\n }\n```\n\nAfter applying the patch, be sure to test its effectiveness by rendering a Slate value containing an `attributes` property on some element.\n\n```ts\n[{\n type: \u0027p\u0027,\n attributes: { \u0027data-vulnerable\u0027: true },\n children: [{ text: \u0027My paragraph\u0027 }],\n}]\n```\n\nIf the patch was successful, the `data-vulnerable=\"true\"` attribute should not be present on any DOM element when the Plate editor is rendered in the browser.",
"id": "GHSA-73rg-f94j-xvhx",
"modified": "2024-09-20T22:07:36Z",
"published": "2024-09-20T14:41:02Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/udecode/plate/security/advisories/GHSA-73rg-f94j-xvhx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47061"
},
{
"type": "WEB",
"url": "https://github.com/udecode/plate/commit/16df6074edac22d56c60e0283eae0740230401c9"
},
{
"type": "PACKAGE",
"url": "https://github.com/udecode/plate"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/package/patch-package"
},
{
"type": "WEB",
"url": "https://yarnpkg.com/cli/patch"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Plate allows arbitrary DOM attributes in element.attributes and leaf.attributes"
}
GHSA-73RG-H54G-X9W7
Vulnerability from github – Published: 2026-03-13 21:31 – Updated: 2026-03-13 21:31Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Noor Alam Magical Addons For Elementor magical-addons-for-elementor allows Stored XSS.This issue affects Magical Addons For Elementor: from n/a through <= 1.4.1.
{
"affected": [],
"aliases": [
"CVE-2026-32429"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-13T19:55:01Z",
"severity": "MODERATE"
},
"details": "Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027) vulnerability in Noor Alam Magical Addons For Elementor magical-addons-for-elementor allows Stored XSS.This issue affects Magical Addons For Elementor: from n/a through \u003c= 1.4.1.",
"id": "GHSA-73rg-h54g-x9w7",
"modified": "2026-03-13T21:31:50Z",
"published": "2026-03-13T21:31:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32429"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/magical-addons-for-elementor/vulnerability/wordpress-magical-addons-for-elementor-plugin-1-4-1-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-73RM-HHH2-W9MF
Vulnerability from github – Published: 2026-08-13 15:34 – Updated: 2026-08-13 15:34Unauthenticated Cross Site Scripting (XSS) in Maspik – Spam blacklist <= 2.9.1 versions.
{
"affected": [],
"aliases": [
"CVE-2026-28003"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-13T14:16:57Z",
"severity": "HIGH"
},
"details": "Unauthenticated Cross Site Scripting (XSS) in Maspik \u2013 Spam blacklist \u003c= 2.9.1 versions.",
"id": "GHSA-73rm-hhh2-w9mf",
"modified": "2026-08-13T15:34:38Z",
"published": "2026-08-13T15:34:38Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-28003"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/contact-forms-anti-spam/vulnerability/wordpress-maspik-spam-blacklist-plugin-2-9-1-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-73RW-H6XR-X6HM
Vulnerability from github – Published: 2022-05-24 17:32 – Updated: 2022-05-24 17:32A vulnerability in the authenticated user web interface of Pulse Connect Secure < 9.1R9 could allow attackers to conduct Cross-Site Scripting (XSS) through the CGI file.
{
"affected": [],
"aliases": [
"CVE-2020-8263"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-10-28T13:15:00Z",
"severity": "MODERATE"
},
"details": "A vulnerability in the authenticated user web interface of Pulse Connect Secure \u003c 9.1R9 could allow attackers to conduct Cross-Site Scripting (XSS) through the CGI file.",
"id": "GHSA-73rw-h6xr-x6hm",
"modified": "2022-05-24T17:32:45Z",
"published": "2022-05-24T17:32:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-8263"
},
{
"type": "WEB",
"url": "https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44601"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-73V2-XP42-4VCQ
Vulnerability from github – Published: 2026-04-14 03:31 – Updated: 2026-04-14 03:31The Form Maker by 10Web plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Matrix field (Text Box input type) in form submissions in all versions up to, and including, 1.15.40. This is due to insufficient input sanitization (sanitize_text_field strips tags but not quotes) and missing output escaping when rendering submission data in the admin Submissions view. This makes it possible for unauthenticated attackers to inject arbitrary JavaScript through a form submission that executes in the browser of an administrator who views the submission details.
{
"affected": [],
"aliases": [
"CVE-2026-4388"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-14T03:16:08Z",
"severity": "HIGH"
},
"details": "The Form Maker by 10Web plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Matrix field (Text Box input type) in form submissions in all versions up to, and including, 1.15.40. This is due to insufficient input sanitization (`sanitize_text_field` strips tags but not quotes) and missing output escaping when rendering submission data in the admin Submissions view. This makes it possible for unauthenticated attackers to inject arbitrary JavaScript through a form submission that executes in the browser of an administrator who views the submission details.",
"id": "GHSA-73v2-xp42-4vcq",
"modified": "2026-04-14T03:31:40Z",
"published": "2026-04-14T03:31:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-4388"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/form-maker/tags/1.15.37/admin/views/FormMakerSubmits.php#L166"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/form-maker/tags/1.15.37/admin/views/FormMakerSubmits.php#L169"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/form-maker/tags/1.15.37/frontend/models/form_maker.php#L2352"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026new=3501693%40form-maker%2Ftrunk\u0026old=3492680%40form-maker%2Ftrunk\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/197449f5-9304-49df-9261-a354145fc00e?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"
}
]
}
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.