Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Cross-Site Scripting in emojione

CVE-2016-1000231GHSA-46m8-42hm-wvvw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (emojione 1.3.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm emojione

    Affected
    <= 1.3.0
    Fixed in
    1.3.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-46m8-42hm-wvvw

  2. Revision 1 · created ·

    Published from osv record GHSA-46m8-42hm-wvvw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2016-1000231

Advisory: Cross-Site Scripting in emojione
IDs: CVE-2016-1000231, GHSA-46m8-42hm-wvvw
Record: https://patchnext.com/advisories/cve-2016-1000231 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: emojione 1.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm emojione: affected <= 1.3.0; fixed in 1.3.1

## Suggested inspection (read-only)
- `npm ls emojione --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on emojione.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-46m8-42hm-wvvw (OSV record GHSA-46m8-42hm-wvvw lists affected ranges: npm emojione >=0 <1.3.1 (fixed))
- Verified: https://github.com/advisories/GHSA-46m8-42hm-wvvw (GitHub-reviewed advisory GHSA-46m8-42hm-wvvw lists affected ranges: npm emojione >=0 <=1.3.0)

Commands are suggestions: review each one before running it.

Loading voting…