Skip to content
Fencer Intel
medium 6.1

CVE-2019-11003 json

Materialize-css vulnerable to Cross-site Scripting in autocomplete component

published 7y ago modified 4mo ago also GHSA-7752-f4gf-94gc , EUVD-2019-0406

cvss
6.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

In Materialize through 1.0.0, XSS is possible via the Autocomplete feature.

Patch / fix

  • npm @materializecss/materialize 1.1.0-alpha

Is CVE-2019-11003 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/Dogfalo/materialize/issues/6286 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub 3.0 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm materialize-css
<=1.0.0
 no fix listed
npm @materializecss/materialize
<1.1.0-alpha
1.1.0-alpha

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.