# CVE-2021-47746: NodeBB Plugin Emoji 3.2.1 - Arbitrary File Write

> Administrative users can exploit directory traversal in the emoji upload API to write arbitrary files to system locations, potentially leading to code execution.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-g674-4q3h-w499

## What is CVE-2021-47746?

CVE-2021-47746 is a high-severity path traversal vulnerability in NodeBB Plugin Emoji, published on 21 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

NodeBB Plugin Emoji 3.2.1 contains an arbitrary file write vulnerability that allows administrative users to write files to arbitrary system locations through the emoji upload API. Attackers with admin access can craft file upload requests with directory traversal to overwrite system files by manipulating the file path parameter.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2021-47746?


## How do I fix CVE-2021-47746?

No fix has been published for CVE-2021-47746 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-47746 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47746 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47746 and fix it if it is affected.

What it is: CVE-2021-47746 is a high-severity path traversal vulnerability in NodeBB Plugin Emoji, published on 21 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47746 exists.

Affected product: NodeBB Plugin Emoji. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-47746/ (Markdown: https://insights.sbomify.com/CVE-2021-47746/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-47746
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-47746
- OSV: https://osv.dev/vulnerability/CVE-2021-47746

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-47746/
Summaries are generated and may contain mistakes; the official description above is the record.