MongoDBDatabase / datastore
CVE-2024-7553
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 · uneditedIncorrect validation of files loaded from a local untrusted directory may allow local privilege escalation if the underlying operating systems is Windows. This may result in the application executing arbitrary behaviour determined by the contents of untrusted files. This issue affects MongoDB Server v5.0 versions prior to 5.0.27, MongoDB Server v6.0 versions prior to 6.0.16, MongoDB Server v7.0 versions prior to 7.0.12, MongoDB Server v7.3 versions prior 7.3.3, MongoDB C Driver versions prior to 1.26.2 and MongoDB PHP Driver versions prior to 1.18.1. Required Configuration: Only environments with Windows as the underlying operating system is affected by this issue
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 confidenceMongoDB Server and its C/PHP drivers contain an incorrect validation flaw when loading files from local untrusted directories on Windows systems. This allows a local attacker to perform privilege escalation by placing malicious files in specific locations that MongoDB will load, resulting in arbitrary code execution with elevated privileges.
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
MongoDBDatabase / datastore
>= 5.0.0, < 5.0.27>= 6.0.0, < 6.0.16>= 7.0.0, < 7.0.12>= 7.3.0, < 7.3.3
C DriverApplication
< 1.26.2
Php DriverApplication
< 1.18.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Windows deploymentRun 'systeminfo | findstr /B /C:"OS Name"' or check OS via 'hostname' output showing WindowsAffected if The system is not running Windows - this vulnerability only affects Windows environments
-
Check MongoDB Server versionRun 'mongod --version' or query the server with 'db.version()' from mongo shellAffected if Version falls within: 5.0.0 to <5.0.27, 6.0.0 to <6.0.16, 7.0.0 to <7.0.12, or 7.3.0 to <7.3.3
-
Check MongoDB C Driver versionQuery driver version via application logs or check library file version (e.g., libmongoc.so or mongoc.dll) with 'file' or properties dialogAffected if Driver version is present and less than 1.26.2
-
Check MongoDB PHP Driver versionRun 'php -m' to list modules and 'php -i | grep mongo' for detailed version, or check phpinfo() outputAffected if PHP driver version is present and less than 1.18.1
-
Identify file loading from untrusted directoriesReview MongoDB configuration file (mongod.conf) for file loading directives and audit directories from which MongoDB loads modules, libraries, or configuration filesAffected if MongoDB is configured to load files, modules, or extensions from directories that are writable by non-privileged users
On Windows systems, if MongoDB Server version, C Driver version, or PHP Driver version falls within the affected ranges AND the database loads files from writable untrusted directories, the environment is vulnerable to local privilege escalation.
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 · scoped1.18.11.26.25.0.27
Upgrade MongoDB Server to version 5.0.27+, 6.0.16+, 7.0.12+, or 7.3.3+ (and C Driver to 1.26.2+/PHP Driver to 1.18.1+ if applicable) on all Windows environments. This vulnerability only affects Windows deployments.
MongoDB Server: upgrade to 5.0.27 / 6.0.16 / 7.0.12 / 7.3.3 (whichever corresponds to your major version); C Driver: upgrade to 1.26.2; PHP Driver: upgrade to 1.18.1
- 1. Identify the currently installed MongoDB Server version using 'db.version()' in the mongo shell or checking the service
- 2. For MongoDB Server on Windows: Stop the MongoDB service using 'net stop MongoDB' or via Services console
- 3. For MongoDB Server on Windows: Back up the data directory (default: C:\data\db) and configuration file (mongod.cfg)
- 4. Download and install the minimum fixed version for your major version line: 5.0.27, 6.0.16, 7.0.12, or 7.3.3 (whichever is applicable) from mongodb.com/downloads
- 5. For MongoDB C Driver (< 1.26.2): Update the driver dependency in your project to version 1.26.2 or later via package manager (e.g., apt, yum, brew)
- 6. For MongoDB PHP Driver (< 1.18.1): Update the PHP extension to version 1.18.1 or later via PECL (pecl install mongodb) and update php.ini if needed
- 7. For MongoDB Server: Restart the MongoDB service using 'net start MongoDB' or via Services console
- 8. Verify the upgrade by checking 'db.version()' confirms the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7553 — 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-2024-7553 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