How severe is CVE-2016-1000231?

No CVSS score has been assigned to CVE-2016-1000231 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2016-1000231?

CVE-2016-1000231 affects the following packages: emojione (npm). Ecosystems affected: npm.

How do I fix CVE-2016-1000231?

Update emojione to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1000231 is resolved across your whole dependency graph.

How do I detect CVE-2016-1000231 in my npm dependencies?

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

How do I mitigate CVE-2016-1000231 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 CVE-2016-1000231 actively exploited in the wild?

No public exploit code has been indexed for CVE-2016-1000231 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 CVE-2016-1000231 published, and has it been updated?

CVE-2016-1000231 was published on September 1, 2020 and was last updated on November 8, 2023. 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

CVE-2016-1000231 — emojione

Fix: joypixels/emojione@613079b

CVE-2016-1000231 is a security vulnerability in emojione. A fix is available for emojione — see the affected versions and patch details below.

Cross-Site Scripting in emojione

Published

Sep 1, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦emojione

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Affected versions of emojione are vulnerable to cross-site scripting when user input is passed into the toShort(), shortnameToImage(), unicodeToImage(), and toImage() functions.

Recommendation

Update to version 1.3.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`emojione`	all versions	1.3.1`npm install emojione@1.3.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for emojione, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update emojione to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1000231 is resolved across your whole dependency graph.
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

Affected versions of `emojione` are vulnerable to cross-site scripting when user input is passed into the `toShort()`, `shortnameToImage()`, `unicodeToImage()`, and `toImage()` functions. ## Recommendation Update to version 1.3.1 or later.

O3 Security · Impact-Aware SCA

Is CVE-2016-1000231 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works