dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7217

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Deepractice PromptX up to 2.4.0. The affected element is the function read_docx/read_xlsx/read_pptx/list_xlsx_sheets/read_pdf of the file packages/mcp-office/src/index.ts of the component Document File Handler. Such manipulation of the argument path leads to absolute path traversal. The attack can be executed 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 · moderate confidence

Absolute path traversal vulnerability in Deepractice PromptX's Document File Handler. The functions read_docx, read_xlsx, read_pptx, list_xlsx_sheets, and read_pdf in packages/mcp-office/src/index.ts accept unsanitized path arguments, allowing remote attackers to access arbitrary files on the system by providing absolute paths outside the intended directory.

MitigationImplement strict input validation and path normalization: validate that resolved paths remain within allowed directories, reject absolute path inputs or strip dangerous path components, and apply allowlist restrictions on accessible file locations.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 if Deepractice PromptX is installed
    Search for the 'promptx' or 'deepractice' package in your environment using 'pip list' or 'npm list' depending on your package manager, or look for the packages/mcp-office directory in your project.
    Affected if The Deepractice PromptX package or mcp-office component is present in your environment.
  2. Locate the mcp-office package version
    Check the version of the mcp-office package in your dependency lock file (package-lock.json, package.json, requirements.txt, or Pipfile) or run 'npm list @deepractice/mcp-office' or 'pip show deep-practice-promptx' if available.
    Affected if The installed version has not been patched for path traversal vulnerabilities in the document handlers.
  3. Verify if vulnerable file handler functions are exposed
    Review your application code or API endpoints that call read_docx, read_xlsx, read_pptx, list_xlsx_sheets, or read_pdf functions from the mcp-office package. Check if these functions accept user-controlled path input.
    Affected if Any of these functions (read_docx, read_xlsx, read_pptx, list_xlsx_sheets, read_pdf) are accessible and accept path parameters without validation.
  4. Inspect the path validation logic in index.ts
    Examine the source code in packages/mcp-office/src/index.ts around the document file handler functions. Look for path validation or sanitization before file operations.
    Affected if The code lacks validation that rejects absolute paths or traversal sequences (../) in the path argument.
  5. Test for path traversal exposure
    If you have access to the function interface, attempt to pass an absolute path like '/etc/passwd' or a path with '../' to any of the vulnerable functions and observe if unauthorized file contents are returned.
    Affected if The functions return contents of files outside the intended directory when given absolute or traversal paths.

You are affected if Deepractice PromptX with the mcp-office package is installed and its document handler functions (read_docx, read_xlsx, read_pptx, list_xlsx_sheets, read_pdf) accept unvalidated path input that allows reading files outside the intended directory.

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 and path normalization: validate that resolved paths remain within allowed directories, reject absolute path inputs or strip dangerous path components, and apply allowlist restrictions on accessible file locations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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