CVE-2026-7159
7.3douinc · mkdocs-mcp-plugin
The mkdocs-mcp-plugin is vulnerable to path traversal via the read_document and list_documents functions in server.py, allowing remote unauthenticated attackers to access arbitrary files.
Executive summary
A path traversal vulnerability in the douinc mkdocs-mcp-plugin allows unauthenticated remote attackers to access unauthorized files, posing a significant risk to data confidentiality.
Vulnerability
This is a path traversal vulnerability (CWE-22) residing in the server.py file. It allows an unauthenticated remote attacker to manipulate the docs_dir or file_path arguments to access files outside of the intended directory structure.
Business impact
The ability for an unauthenticated attacker to perform path traversal can lead to the unauthorized exposure of sensitive configuration files, source code, or internal system data. With a CVSS score of 7.3, this vulnerability represents a high-risk security flaw that could facilitate further reconnaissance or compromise the integrity of the hosting environment.
Remediation
Immediate Action: As there is currently no official patch available, administrators should restrict network access to the affected service or disable the plugin until the vendor releases a secure update.
Proactive Monitoring: Monitor server access logs for anomalous requests containing path traversal patterns, such as sequences of dot-dot-slash (../) characters targeting the plugin endpoints.
Compensating Controls: Implement a Web Application Firewall (WAF) rule to inspect and block requests that attempt to traverse directories via input parameters within the mkdocs-mcp-plugin endpoints.
Exploitation status
Public Exploit Available: Yes, a published proof-of-concept exists via the technical write-up in the linked GitHub issue (https://github.com/douinc/mkdocs-mcp-plugin/issues/6).
Analyst recommendation
This vulnerability is serious due to its unauthenticated nature and the presence of a public proof-of-concept. Organizations utilizing the mkdocs-mcp-plugin should prioritize mitigating this risk by limiting exposure, as the vendor fix is still pending. Once the vendor releases the update, it must be applied immediately to restore a secure posture.
Sources
Originally found and disclosed by SmallW (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.