dbcve.org
CWE-494Weakness · CWE-494

CVE-2021-47987

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Parse Server before 4.10.0 experienced a supply chain incident where unauthorized version tags were pushed to the official repository, pointing to an unreviewed personal fork from a contributor with write access. Projects using git-based dependencies referencing these affected tags (e.g., parse-server#4.9.3) may have incorporated unvetted code. While no malicious code was confirmed, the introduction of security vulnerabilities could not be ruled out.

MitigationReview all dependency configurations to identify and remove any git-based dependencies referencing the affected Parse Server tags, then update to version 4.10.0 or later from official release channels.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Parse Server dependency in package.json
    Inspect the project's package.json file and locate any entry for 'parse-server' in the dependencies or devDependencies object
    Affected if parse-server is listed as a dependency
  2. Determine if using git-based dependency
    Check if the parse-server dependency uses a git URL, github shorthand, or has a 'from' field pointing to a git repository instead of a version number
    Affected if The dependency uses git-based installation (e.g., git://, https://git..., github:owner/repo, or a 'from' field with a git URL)
  3. Extract the git reference being used
    For git-based dependencies, note the specific tag, branch, or commit hash referenced (e.g., after the # symbol in 'parse-server#4.9.3' or in the 'resolved' or 'from' fields)
    Affected if A specific git reference (tag or branch) is declared
  4. Verify the source repository
    Examine the git URL or github shorthand to determine if it points to the official parse-server repository (typically 'parsecommunity/parse-server') or an alternative source
    Affected if The source is not the official parse-server repository or uses an unofficial tag reference
  5. Compare referenced version to affected range
    If using an official tag, compare it to the affected versions (before 4.10.0). Note that some tags in the affected range may have been pushed as part of the supply chain incident
    Affected if The referenced version is 4.10.0 or later from official releases, or if using git-based dependency with affected tags before 4.10.0

A user is affected if their project uses a git-based dependency reference to Parse Server versions before 4.10.0, particularly if the reference points to tags that were pushed during the unauthorized incident.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review all dependency configurations to identify and remove any git-based dependencies referencing the affected Parse Server tags, then update to version 4.10.0 or later from official release channels.

Recommended fix Moderate confidence

Parse Server 4.10.0 or later (official npm release)

  1. Audit your project's dependency configuration (package.json, package-lock.json, or equivalent) to check if parse-server is referenced as a git-based dependency (e.g., 'parse-server#4.9.3' or similar tag-based git URLs)
  2. If git-based dependencies to parse-server are found, remove them from your dependency configuration
  3. Update your parse-server dependency to use the official released version 4.10.0 or later (e.g., 'npm install parse-server@^4.10.0' or equivalent package manager command)
  4. Reinstall dependencies to ensure the official released version is installed
  5. Verify the installed parse-server version matches the intended stable release
Caveat Not specified in the provided description; review Parse Server 4.10.0 release notes for any relevant changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-47987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-47987 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data