# CVE-2021-47987: Parse Server - Arbitrary Code Execution via Malicious Version Tags

> Attackers could inject malicious code into Parse Server projects using specific git-based dependencies due to unreviewed version tags.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-h6qh-8r3c-pc9v

## What is CVE-2021-47987?

CVE-2021-47987 is a high-severity vulnerability in parse-community parse-server, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Parse Server before 4.10.0 was affected by a supply chain incident in which incorrect version tags were pushed to the official repository pointing to an unreviewed personal fork of a contributor with write access. No releases were published with these tags; a project was exposed only if it defined a git-based dependency referencing one of the affected tags (for example, parse-server#4.9.3). The code behind the tags was not reviewed or approved, and although no malicious code was identified, the introduction of security vulnerabilities could not be ruled out.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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


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

Upgrade to a fixed version.

## Is CVE-2021-47987 being exploited?

There is no known exploitation of CVE-2021-47987 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2021-47987 is a high-severity vulnerability in parse-community parse-server, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-47987 in the wild and no public exploit code.

Affected product: parse-community parse-server. 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-47987/ (Markdown: https://insights.sbomify.com/CVE-2021-47987/index.md)
```

## Sources

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

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