dbcve.org
Doris Mcp ServerApplication · Apache

CVE-2025-58337

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-05
Fix available
A fix is available. Upgrade to 0.6.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
An attacker with a valid read-only account can bypass Doris MCP Server’s read-only mode due to improper access control, allowing modifications that should have been prevented by read-only restrictions. Impact: Bypasses read-only mode; attackers with read-only access may perform unauthorized modifications. Recommended action for operators: Upgrade to version 0.6.0 as soon as possible (this release contains the fix).

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

Doris MCP Server contains an improper access control vulnerability where read-only mode can be bypassed by authenticated users with read-only permissions. This allows attackers to perform modification operations that should be restricted under read-only mode, exploiting a flaw in the server's permission enforcement logic.

MitigationUpgrade Doris MCP Server to version 0.6.0 immediately to apply the access control fix that enforces read-only restrictions properly.

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
Doris Mcp ServerApplication
Affected:< 0.6.0

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 Doris MCP Server version
    Run 'doris-mcp-server --version' or check the installed package version via your package manager (e.g., 'pip show doris-mcp-server' or 'docker images'). Compare the version number to the affected range: versions prior to 0.6.0 are vulnerable.
    Affected if The installed version is any version before 0.6.0
  2. Locate configuration file
    Find the MCP server configuration file (commonly in /etc/doris-mcp/, ~/.doris-mcp/, or alongside the server binary). Look for files named config.yaml, config.json, or settings.yaml.
    Affected if A configuration file exists and read-only mode settings are present
  3. Verify read-only mode is enabled
    Inspect the configuration file for a read-only flag, permission level, or access mode setting. Common keys include 'read_only', 'readonly_mode', 'permission', or 'access_level'. Confirm the value indicates read-only restriction is intended.
    Affected if Read-only mode is explicitly configured as enabled (e.g., 'read_only: true')
  4. Check authentication is enforced
    Review the configuration for authentication settings. Verify that user authentication is required (e.g., 'auth_enabled: true', 'require_auth: true', or an authentication backend is configured).
    Affected if Authentication is enabled and users must authenticate with credentials
  5. Confirm authorization model includes read-only roles
    Examine the permission or role configuration to determine if distinct read-only roles or permissions exist that should be restricted from modification operations.
    Affected if The system defines read-only user roles or permissions that should be enforced separately from admin roles

Your environment is affected if the installed Doris MCP Server version is before 0.6.0 AND read-only mode is configured, since the vulnerability allows authenticated read-only users to bypass those restrictions.

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
Upgrade available Upgrade to 0.6.0 or later
Fixed in 0.6.0
Interim mitigation

Upgrade Doris MCP Server to version 0.6.0 immediately to apply the access control fix that enforces read-only restrictions properly.

Recommended fix High confidence

0.6.0

  1. 1. Check current Doris MCP Server version using your package manager or deployment method
  2. 2. Stop the Doris MCP Server service
  3. 3. Upgrade to version 0.6.0 using your installation method (e.g., pip install doris-mcp-server==0.6.0, container image pull, or package manager)
  4. 4. Verify the new version is installed correctly
  5. 5. Restart the Doris MCP Server service
  6. 6. Test that read-only mode properly restricts write operations

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

Fix this in Doris Mcp Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

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