CVE-2019-10758
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 · uneditedmongo-express before 0.54.0 is vulnerable to Remote Code Execution via endpoints that uses the `toBSON` method. A misuse of the `vm` dependency to perform `exec` commands in a non-safe environment.
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 confidencemongo-express before 0.54.0 contains a Remote Code Execution vulnerability where the `toBSON` method improperly uses the Node.js `vm` module to execute commands in an unsafe manner, allowing unauthenticated remote attackers to run arbitrary code on the host.
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< 0.54.0CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate mongo-express installationSearch for mongo-express in your application's dependencies: check package.json, package-lock.json, or run 'npm list mongo-express' in the project directoryAffected if mongo-express is listed as a dependency with a version number less than 0.54.0
-
Identify running mongo-express versionIf mongo-express is running as a service, check the version displayed in the web interface header or query the service process for its installed version using the package managerAffected if The running instance reports version lower than 0.54.0
-
Verify the toBSON endpoint is reachableCheck if your mongo-express web interface is accessible over the network on its default port (8081) or configured port. The vulnerable endpoints utilize the toBSON serialization methodAffected if The mongo-express web interface is network-accessible and the version is below 0.54.0, making the vm module exploitation possible
You are affected if mongo-express version below 0.54.0 is installed or running and the web interface is accessible, as the unsafe vm module usage in toBSON endpoints can be exploited for remote code execution.
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 · scoped0.54.0
Upgrade mongo-express to version 0.54.0 or later which properly secures the `vm` module usage.
0.54.0
- 1. Identify the current mongo-express version by running `npm list mongo-express` or checking package.json
- 2. Update the mongo-express dependency in package.json to version 0.54.0 or later: `npm install mongo-express@^0.54.0 --save`
- 3. Run `npm install` to update lockfile and install the new version
- 4. Verify the installation succeeded by running `npm list mongo-express` and confirming version 0.54.0 or higher is installed
- 5. Test the application functionality in a staging environment to ensure the upgrade does not break existing features
- 6. Deploy the updated application to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10758 — 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-2019-10758 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