How severe is GHSA-hgr5-82rc-p936?

No CVSS score has been assigned to GHSA-hgr5-82rc-p936 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hgr5-82rc-p936?

GHSA-hgr5-82rc-p936 affects the following packages: md-data-table (npm). Ecosystems affected: npm.

How do I fix GHSA-hgr5-82rc-p936?

No patched version of md-data-table has shipped for GHSA-hgr5-82rc-p936 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-hgr5-82rc-p936 in my npm dependencies?

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

How do I mitigate GHSA-hgr5-82rc-p936 if there is no patch (or I can't update yet)?

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.

Is GHSA-hgr5-82rc-p936 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hgr5-82rc-p936 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-hgr5-82rc-p936 published, and has it been updated?

GHSA-hgr5-82rc-p936 was published on September 1, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Cross-Site Scripting in md-data-tableGHSA-hgr5-82rc-p936

GHSA-hgr5-82rc-p936 is a security vulnerability in md-data-table. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

md-data-tablenpm

85downloads / week

Description

All versions of md-data-table are vulnerable to cross-site scripting (XSS). This vulnerability is exploitable if an attacker has control over data that is rendered by mdt-row

Recommendation

As there is no fix for this vulnerability at this time we recommend either selecting another package to perform this functionality or properly sanitizing all user data prior to rendering with md-data-table

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`md-data-table`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for md-data-table, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of md-data-table has shipped for GHSA-hgr5-82rc-p936 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 `md-data-table` are vulnerable to cross-site scripting (XSS). This vulnerability is exploitable if an attacker has control over data that is rendered by `mdt-row` ## Recommendation As there is no fix for this vulnerability at this time we recommend either selecting another package to perform this functionality or properly sanitizing all user data prior to rendering with `md-data-table`

O3 Security · Impact-Aware SCA

Is GHSA-hgr5-82rc-p936 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works