Is CVE-2019-11004 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2019-11004 being exploited in the wild.

How severe is CVE-2019-11004?

Low severity, with a CVSS score of 3, published 9 April 2019.

Which products and versions are affected?

Materialize before 1.1.0-alpha; @materializecss/materialize (npm) SEMVER:introduced=0,fixed=1.1.0-alpha; materialize-css (npm) SEMVER:introduced=0,last_affected=1.0.0.

Is there a fix for CVE-2019-11004?

Yes. @materializecss/materialize (npm): upgrade to 1.1.0-alpha or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2019-11004 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2019-11004?

Check whether you run Materialize, @materializecss/materialize (npm) or materialize-css (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2019-11004: Materialize-css XSS in Toast feature

CVE-2019-11004 · Severity: low · CVSS 3 · Published 2019-04-09

Materialize-css is a popular CSS framework providing UI components like toasts, tooltips, and autocomplete. The framework fails to sanitize untrusted HTML input before rendering these components, allowing an attacker to inject malicious scripts that execute in users' browsers and steal sensitive data like cookies or session tokens.

Technologies: @materializecss/materialize (npm), materialize-css (npm). Vendors: npm.

Quick answers

Is CVE-2019-11004 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2019-11004 being exploited in the wild.
How severe is CVE-2019-11004?: Low severity, with a CVSS score of 3, published 9 April 2019.
Which products and versions are affected?: Materialize before 1.1.0-alpha; @materializecss/materialize (npm) SEMVER:introduced=0,fixed=1.1.0-alpha; materialize-css (npm) SEMVER:introduced=0,last_affected=1.0.0.
Is there a fix for CVE-2019-11004?: Yes. @materializecss/materialize (npm): upgrade to 1.1.0-alpha or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2019-11004 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2019-11004?: Check whether you run Materialize, @materializecss/materialize (npm) or materialize-css (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@materializecss/materialize (npm): upgrade to 1.1.0-alpha or later
```
npm install @materializecss/materialize@1.1.0-alpha
```

Technical details

Materialize-css versions through 1.0.0 contain a Cross-Site Scripting (XSS) vulnerability in the Toast, Tooltip, and Autocomplete components due to improper neutralization of input during web page generation (CWE-79). The vulnerable code uses jQuery's .html() method or equivalent to render user-supplied data directly into the DOM without sanitization. An attacker can inject malicious HTML and JavaScript through dynamic content (e.g., user-supplied messages displayed in toasts, tooltip text, or autocomplete suggestions). The attack requires user interaction in the web page but no prior authentication. A fix is available in version 1.1.0-alpha of the @materializecss/materialize package.

Affected products

Materialize materialize-css through 1.0.0
Materialize materialize before 1.1.0-alpha

Identifiers

CVE-2019-11004
GHSA-rg3q-jxmp-pvjj

Timeline

2019-02-08: disclosed: Vulnerability reported via GitHub issue #6286
2019-04-09: advisory: GHSA-rg3q-jxmp-pvjj published

References

https://github.com/Dogfalo/materialize/issues/6286

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.