dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7627

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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
A security vulnerability has been detected in 8nite metatrader-4-mcp 1.0.0. This vulnerability affects the function CallToolRequestSchema of the file src/index.ts of the component sync_ea_from_file. Such manipulation of the argument ea_name leads to path traversal. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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 confidence

A path traversal vulnerability exists in the sync_ea_from_file component of metatrader-4-mcp 1.0.0. The CallToolRequestSchema function in src/index.ts fails to properly validate the ea_name argument, allowing attackers to use directory traversal sequences (e.g., ../../../) to access files outside the intended directory.

MitigationImplement strict input validation on the ea_name parameter using allowlist validation or canonicalize paths and verify they resolve within an allowed directory. Ensure the function rejects any input containing path traversal sequences.

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

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

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. Confirm metatrader-4-mcp is installed
    Check for the package in node_modules or inspect package.json dependencies
    Affected if The package metatrader-4-mcp is present in the environment
  2. Verify the installed version
    Run 'npm list metatrader-4-mcp' or check the version field in package.json
    Affected if The version is 1.0.0
  3. Locate the vulnerable source file
    Find src/index.ts within the metatrader-4-mcp package directory
    Affected if The file src/index.ts exists and contains the CallToolRequestSchema function
  4. Inspect ea_name input validation
    Examine the CallToolRequestSchema function in src/index.ts for how it handles the ea_name parameter
    Affected if The code does not validate or sanitize the ea_name argument for path traversal sequences like ../
  5. Verify sync_ea_from_file is exposed
    Check if the sync_ea_from_file tool is registered in the package and accessible to users
    Affected if The sync_ea_from_file component is enabled and callable

A user is affected if they have metatrader-4-mcp version 1.0.0 installed with the CallToolRequestSchema function in src/index.ts that lacks validation on the ea_name parameter for directory traversal sequences.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the ea_name parameter using allowlist validation or canonicalize paths and verify they resolve within an allowed directory. Ensure the function rejects any input containing path traversal sequences.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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