Skip to content

← Actionable
High, CVSS 8.8amended

@andrea9293/mcp-documentation-server: Web UI API binds to all interfaces without authentication by default

CVE-2026-54504GHSA-6f5r-5672-72j7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@andrea9293/mcp-documentation-server 1.13.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-54504: 0.57% estimated exploitation activity in the next 30 days; percentile 47.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary @andrea9293/mcp-documentation-server v1.13.0 documents that a Web UI starts automatically on port 3080. However, the Web UI/API appears to bind to all network interfaces by default (:3080 / 0.0.0.0:3080) instead of localhost-only, and its document-management API endpoints do not require authentication. As a result, any network-reachable client on the same LAN, VM network, or container bridge can access the document-admin API without credentials. In my reproduction, I was able to enumerate documents, add a document, read its full content, search across the corpus, and delete the document through the host's LAN IP. The issue is not that a Web UI exists. The issue is that a local document-management Web UI/API is exposed on all interfaces by default without authentication. Details The README documents that the Web UI starts automatically and tells users to open: It also documents STARTWEBUI=true and WEBPORT=3080 as the defaults. The vulnerable behavior appears to come from…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-6f5r-5672-72j7

  2. Revision 1 · created ·

    Published from osv record GHSA-6f5r-5672-72j7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54504

Advisory: @andrea9293/mcp-documentation-server: Web UI API binds to all interfaces without authentication by default
IDs: CVE-2026-54504, GHSA-6f5r-5672-72j7
Record: https://patchnext.com/advisories/cve-2026-54504 (revision 2, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @andrea9293/mcp-documentation-server 1.13.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @andrea9293/mcp-documentation-server: affected >= 1.13.0, <= 1.13.0; fixed in 1.13.1

## Suggested inspection (read-only)
- `npm ls @andrea9293/mcp-documentation-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @andrea9293/mcp-documentation-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6f5r-5672-72j7 (OSV record GHSA-6f5r-5672-72j7 lists affected ranges: npm @andrea9293/mcp-documentation-server >=1.13.0 <1.13.1 (fixed))
- Verified: https://github.com/advisories/GHSA-6f5r-5672-72j7 (GitHub-reviewed advisory GHSA-6f5r-5672-72j7 lists affected ranges: npm @andrea9293/mcp-documentation-server >=1.13.0 <=1.13.0)

Commands are suggestions: review each one before running it.

Loading voting…