Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-7417

HIGH · 7.3 CVSS v3.1 Published 2026-04-29

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

82/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

A vulnerability was found in Algovate xhs-mcp 0.8.11. This affects the function xhs_publish_content of the file src/server/mcp.server.ts of the component MCP Interface. Performing a manipulation of the argument media_paths results in server-side request forgery. The attack may be initiated remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary

dbcve analysis · high confidence

Server-side request forgery (SSRF) vulnerability in Algovate xhs-mcp v0.8.11 allows remote attackers to make the server perform arbitrary requests via the media_paths parameter in the xhs_publish_content function within the MCP Interface (src/server/mcp.server.ts). The function does not validate or restrict the media_paths input before using it to fetch content, enabling attackers to target internal services or external resources.

MitigationImplement strict input validation on the media_paths parameter to restrict URLs/paths to expected sources only, combined with network segmentation to prevent the server from connecting to internal services or unauthorized external endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify xhs-mcp installation exists

Locate the Algovate xhs-mcp package in your environment - check node_modules, package directories, or the application installation folder. Look for the xhs-mcp or algovate package.

Affected if The package is not found, you are not using this product.
Confirm installed version is 0.8.11

Run a version check command such as npm list xhs-mcp, pip show xhs-mcp, or check your package.json/package-lock.json for the xhs-mcp version entry.

Affected if Your installed version is exactly 0.8.11, you are running the affected version.
Check if MCP Interface is enabled

Examine your server configuration or startup settings. Look for MCP server initialization in src/server/mcp.server.ts or configuration that enables the MCP Interface endpoint.

Affected if The MCP Interface is disabled or not configured, the vulnerable code path may not be exposed.
Verify xhs_publish_content function is exposed

Review your MCP server's exposed methods or API endpoints. Check if xhs_publish_content is listed as an available function callable via the MCP Interface.

Affected if The xhs_publish_content function is publicly accessible via the MCP Interface, the media_paths parameter can be exploited.
Check if external input to media_paths is possible

Inspect how the xhs_publish_content function receives the media_paths parameter. Determine if untrusted input can be passed to this parameter from external sources or users.

Affected if External or untrusted input can reach the media_paths parameter, SSRF exploitation is possible.

You are affected if you are running Algovate xhs-mcp version 0.8.11 with the MCP Interface enabled and the xhs_publish_content function exposed to external input via the media_paths parameter.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement strict input validation on the media_paths parameter to restrict URLs/paths to expected sources only, combined with network segmentation to prevent the server from connecting to internal services or unauthorized external endpoints.

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-7417 — 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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7417 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-7417?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.4%

Remediation

A high-priority fix

Have this fixed 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-7417 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References