Skip to main content
VulnerabilityPublished

CVE-2025-59333: executeautomation mcp-database-server · Improper Access Control

Affects executeautomation mcp-database-serverSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
executeautomation mcp-database-serverAffected
  • <=1.1.0
Fixed in–

AI-suggested

1. Immediate assessment of all systems using the @executeautomation/database-server npm package version 1.1.0 or earlier is critical. Identify and inventory all instances to understand exposure. 2. Where possible, upgrade to a fixed version once available from the vendor or consider switching to alternative distributions of the mcp-database-server that are not affected by this vulnerability. 3. Implement network-level controls such as firewall rules and segmentation to restrict access to the mcp-database-server instances only to trusted hosts and networks, minimizing exposure to external attackers. 4. Enforce strict authentication and authorization policies on the database and server layers to limit the privileges of users and services interacting with the mcp-database-server. 5. Monitor logs and network traffic for unusual activities indicative of exploitation attempts, such as unexpected write operations or service disruptions. 6. Consider deploying Web Application Firewalls (WAFs) or Intrusion Detection/Prevention Systems (IDS/IPS) with rules tailored to detect and block exploitation patterns targeting this vulnerability. 7. Engage with the vendor or community to track patch releases and apply updates promptly once available. 8. Conduct security awareness and training for developers and system administrators to understand the risks associated with improper access controls and the importance of secure configuration.

Description

The mcp-database-server (MCP Server) 1.1.0 and earlier, as distributed via the npm package @executeautomation/database-server, fails to implement adequate security controls to properly enforce a "read-only" mode. This vulnerability affects only the npm distribution; other distributions are not impacted. As a result, the server is susceptible to abuse and attacks on affected database systems such as PostgreSQL, and potentially others that expose elevated functionalities. These attacks may lead to denial of service and other unexpected behaviors.

References

Community reviews

Loading reviews…