dbcve.org
Parse ServerApplication · Parseplatform

CVE-2021-47986

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 8 weeks old

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 contains a supply chain vulnerability where incorrect version tags were pushed to the repository linking to unreviewed code in a personal fork. Attackers could exploit this by specifying affected version tags in dependency declarations to execute unreviewed and potentially malicious code.

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 · high confidence

Supply chain vulnerability in Parse Server before 4.10.0 where incorrect version tags were pushed to the repository linking to unreviewed code in a personal fork. Attackers could exploit this by specifying affected version tags in dependency declarations to execute unreviewed and potentially malicious code.

MitigationUpdate to Parse Server 4.10.0 or later and audit all dependency declarations to ensure no affected version tags pointing to the malicious fork are in use.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Parse ServerApplication
Affected:= 4.0.0= 4.0.3= 4.0.4= 4.0.6= 4.0.7= 4.0.8= 4.0.9= 4.0.10= 4.0.11= 4.0.12= 4.0.13= 4.0.14

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 installed Parse Server version
    Run 'npm list parse-server' or inspect the 'dependencies' or 'devDependencies' section in your project's package.json file
    Affected if The installed version is earlier than 4.10.0 (e.g., 4.9.x, 4.8.x, etc.)
  2. Review dependency declarations for version tags
    Search package.json and package-lock.json for any parse-server entries that specify version tags rather than semver ranges (e.g., 'v4.10.0', 'release-4.9', or non-standard tag formats)
    Affected if Any dependency declaration uses a tag that points to the compromised fork rather than an official release
  3. Audit package-lock.json integrity
    Examine the resolved URL in package-lock.json for parse-server entries. Look for any 'resolved' or 'integrity' fields pointing to repositories other than the official Parse Server npm registry
    Affected if Dependencies resolve to a non-official Parse Server repository or show unexpected source URLs
  4. Check for recent unexpected dependency changes
    Review git history or dependency change logs (package-lock.json diffs) for any recent additions of Parse Server version tags that were not part of official releases
    Affected if Recent commits or lockfile changes introduce version tags corresponding to the compromised period (before 4.10.0)

You are affected if your Parse Server installation version is earlier than 4.10.0 OR if any dependency declarations reference version tags from the compromised repository rather than official releases.

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

Update to Parse Server 4.10.0 or later and audit all dependency declarations to ensure no affected version tags pointing to the malicious fork are in use.

Recommended fix Moderate confidence

Parse Server 4.10.0 or later

  1. 1. Review the Parse Server 4.10.0 release notes and changelog to understand any potential breaking changes
  2. 2. Create a backup of your current Parse Server database and configuration
  3. 3. Update your Parse Server dependency to version 4.10.0 or later (e.g., npm install parse-server@^4.10.0 or update your package.json)
  4. 4. Test the upgrade in a staging environment before deploying to production
  5. 5. Deploy the updated version to production
Caveat Review Parse Server 4.10.0 changelog for any breaking changes before upgrading

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

Fix this in Parse Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-47986 — 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-47986 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