Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Cross-Site Scripting Vulnerability in @joeattardi/emoji-buttonGHSA-f34m-x9pj-62vq

HIGHFix: joeattardi/emoji-button@05970c0

GHSA-f34m-x9pj-62vq is a high-severity (CVSS 7.6) Cross-site Scripting (XSS) vulnerability in @joeattardi/emoji-button. A fix is available for @joeattardi/emoji-button — see the affected versions and patch details below.

Also known asCVE-2021-43785
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk
0.00%0.52%1.03%1.55%0.4%1.0%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-f34m-x9pj-62vq by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@joeattardi/emoji-buttonnpm
29Kdownloads / week

Description

Impact

There are two vectors for XSS attacks with versions of @joeattardi/emoji-button before 4.6.2:

  • A URL for a custom emoji
  • An i18n string

In both of these cases, a value can be crafted such that it can insert a script tag into the page and execute malicious code.

Patches

This vulnerability is fixed starting in version 4.6.2. This is resolved by properly escaping strings that are inserted into the HTML document.

Workarounds

There is no workaround other than upgrading to a non-vulnerable version.

Credit

This issue was discovered by GitHub team member @erik-krogh (Erik Krogh Kristensen) and was reported by the GitHub Security Lab team.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@joeattardi/emoji-buttonall versions4.6.2npm install @joeattardi/emoji-button@4.6.2

Affected Products

1 product · 1 configurations
Application
emoji buttonemoji_button_project
< 4.6.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update @joeattardi/emoji-button to 4.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f34m-x9pj-62vq is resolved across your whole dependency graph.

  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

### Impact There are two vectors for XSS attacks with versions of @joeattardi/emoji-button before 4.6.2: - A URL for a custom emoji - An i18n string In both of these cases, a value can be crafted such that it can insert a `script` tag into the page and execute malicious code. ### Patches This vulnerability is fixed starting in version 4.6.2. This is resolved by properly escaping strings that are inserted into the HTML document. ### Workarounds There is no workaround other than upgrading to a non-vulnerable version. ### Credit This issue was discovered by GitHub team member [@erik-krog
O3 Security · Impact-Aware SCA

Is GHSA-f34m-x9pj-62vq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Cross-Site Scripting Vulnerability in @joeattardi/emoji-butt…