NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2019-11003 — materialize-css

MEDIUMFix: materializecss/materialize#49

CVE-2019-11003 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in materialize-css. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for materialize-css — see the affected versions and patch details below.

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

Also known asGHSA-7752-f4gf-94gc
Published
Updated
Affected
2 pkgs
Patched
1 / 2
Exploits
1 known
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk
0.00%0.43%0.86%1.29%0.2%0.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

216other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
materialize-cssnpm
18Kdownloads / week
@materializecss/materializenpm
3Kdownloads / week

Description

All versions of materialize-css are vulnerable to Cross-Site Scripting. The autocomplete component does not sufficiently sanitize user input, allowing an attacker to execute arbitrary JavaScript code if the malicious input is rendered by a user.

Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmaterialize-cssall versionsNo fix
📦npm@materializecss/materializeall versions1.1.0-alphanpm install @materializecss/materialize@1.1.0-alpha

Affected Products

1 product · 1 configurations
Application
materializematerializecss
≤ 1.0.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Materialize through 1.0.0, XSS is possible via the Autocomplete featu…

github.comNVDApr 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for materialize-css, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for CVE-2019-11003; check the affected-versions list above or the advisory for the patched release of materialize-css, then make sure no transitive dependency still pins the vulnerable range.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

All versions of `materialize-css` are vulnerable to Cross-Site Scripting. The `autocomplete` component does not sufficiently sanitize user input, allowing an attacker to execute arbitrary JavaScript code if the malicious input is rendered by a user. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.
O3 Security · Impact-Aware SCA

Is CVE-2019-11003 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-11003: materialize-css XSS — Fixed in 1.1.0-alpha