dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-12100

HIGH · 7.8 CVSS v3.1 Published 2025-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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
Incorrect Default Permissions vulnerability in MongoDB BI Connector ODBC driver allows Privilege Escalation.This issue affects BI Connector ODBC driver: from 1.0.0 through 1.4.6.

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

The MongoDB BI Connector ODBC driver ships with overly permissive default file and directory permissions, allowing local unprivileged users to modify executable files or configuration data and escalate privileges to higher authority levels.

MitigationApply vendor-provided patches when available; otherwise, manually harden file and directory permissions on the BI Connector ODBC driver installation to follow least-privilege principles.

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
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 checks

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

  1. Locate the MongoDB BI Connector ODBC driver installation
    Search for common installation paths such as /opt/mongodb/bi-connector, C:\Program Files\MongoDB\BI Connector, or check the system PATH for mongodq and mongosql binaries. Use 'where mongodq' on Windows or 'which mongodq' on Linux. Check Program Files directories for MongoDB folders.
    Affected if The BI Connector ODBC driver is installed on the system
  2. List file and directory permissions on the installation root
    Run 'ls -la' (Linux/macOS) or 'icacls' (Windows) on the MongoDB BI Connector installation directory. Look for permissions that grant Write or Modify access to Users, Everyone, or other unprivileged groups.
    Affected if Any unprivileged user or group has write/modify permissions to the installation directory or its contents
  3. Check permissions on executable files
    Run 'ls -la' on binary files such as mongodq.exe, mongosql.exe, or related .dll files in the bin directory. Verify if non-admin users have Write or Execute permissions that could allow modification or replacement.
    Affected if Executable files are writable or modifiable by unprivileged users
  4. Inspect configuration file permissions
    Locate and check permissions on configuration files in the BI Connector installation directory, such as mongodq.conf, mongosql.conf, or any .ini/.yaml/.json config files. Use 'ls -la' or 'icacls' to verify write access.
    Affected if Configuration files are writable by unprivileged users, allowing modification of driver settings or connection parameters
  5. Test write access with a non-privileged account
    If possible, use a standard user account to attempt creating or modifying a test file in the BI Connector installation directory. This confirms whether the permission vulnerability is exploitable.
    Affected if A non-administrator user can create or modify files in the installation directory

If the MongoDB BI Connector ODBC driver is installed and any unprivileged user or group has write or modify permissions to the installation directory, executables, or configuration files, the system is affected by this vulnerability.

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

Apply vendor-provided patches when available; otherwise, manually harden file and directory permissions on the BI Connector ODBC driver installation to follow least-privilege principles.

Recommended fix Moderate confidence

Upgrade to BI Connector ODBC driver version greater than 1.4.6 (check MongoDB's official release notes for the specific fixed version)

  1. 1. Identify the current installed version of MongoDB BI Connector ODBC driver
  2. 2. Uninstall or remove the current BI Connector ODBC driver version (1.0.0 through 1.4.6)
  3. 3. Download the latest stable release of MongoDB BI Connector ODBC driver from the official MongoDB download center
  4. 4. Install the new version following MongoDB's installation documentation
  5. 5. Verify the installed version matches the expected fixed release
  6. 6. Test that BI Connector functionality works correctly with the new driver
Caveat Review MongoDB release notes for any compatibility changes or migration requirements between 1.4.x and the target version

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

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

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 locally
dbcve dependency scanner

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