CVE-2022-24760
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 · uneditedParse Server is an open source http web server backend. In versions prior to 4.10.7 there is a Remote Code Execution (RCE) vulnerability in Parse Server. This vulnerability affects Parse Server in the default configuration with MongoDB. The main weakness that leads to RCE is the Prototype Pollution vulnerable code in the file `DatabaseController.js`, so it is likely to affect Postgres and any other database backend as well. This vulnerability has been confirmed on Linux (Ubuntu) and Windows. Users are advised to upgrade as soon as possible. The only known workaround is to manually patch your installation with code referenced at the source GHSA-p6h4-93qp-jhcm.
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 confidenceParse Server versions prior to 4.10.7 contain a Prototype Pollution vulnerability in DatabaseController.js that enables Remote Code Execution. This vulnerability affects the default configuration with MongoDB and likely impacts Postgres and other database backends. The RCE has been confirmed on both Linux (Ubuntu) and Windows systems.
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< 4.10.7CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Parse Server versionRun 'npm list parse-server' in the project directory, or check the version field in package.json, or query the Parse Server health endpointAffected if The installed version is lower than 4.10.7 (e.g., 4.10.6, 4.10.5, etc.)
-
Locate DatabaseController.jsFind the DatabaseController.js file in the Parse Server installation under node_modules/parse-server/lib/Controllers/ or the equivalent path in the sourceAffected if The file exists and originates from a Parse Server version below 4.10.7
-
Verify MongoDB is the configured databaseCheck the Parse Server configuration (server.js, parse-server.json, or environment variables) for the databaseAdapter or databaseURI setting pointing to MongoDBAffected if MongoDB is the active database adapter in the default configuration
-
Check if object injection parameters are reachableInspect API request handling for user-controlled input that could be passed to the database layer where DatabaseController processes query optionsAffected if The Parse Server accepts JSON input that reaches DatabaseController without sanitization of __proto__ or constructor properties
A user is affected if their Parse Server installation is version 4.10.6 or earlier, uses MongoDB (especially in default configuration), and accepts API requests that can reach the vulnerable code path in DatabaseController.js.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.10.7
Upgrade Parse Server to version 4.10.7 or later. If immediate upgrading is not feasible, apply the manual patch referenced in GHSA-p6h4-93qp-jhcm.
4.10.7
- Upgrade Parse Server to version 4.10.7 or later
- If using npm, run: npm install parse-server@^4.10.7
- If using yarn, run: yarn add parse-server@^4.10.7
- Verify the upgrade was successful by checking the version: parse-server --version
- Restart the Parse Server service to apply the changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-24760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24760 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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