/

CVE-2026-75332

Severity:

CRITICAL RISK

(9.1)

SSRF (CWE-918) in Zyplayer-Doc WikiPageWebService API

CVE-2026-75332

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized server-side network access

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Zyplayer-Doc contains a server-side request forgery vulnerability in the WikiPageWebService.download() functionality. If an attacker can invoke the affected download operation with a controllable destination, the server may make requests to internal services or other network locations on the attacker's behalf.

Affected context

The vulnerability occurs in Zyplayer-Doc deployments that expose or otherwise make reachable the WikiPageWebService.download() operation and allow request-related destination data to influence outbound connections. Risk depends on network placement, authentication controls, egress restrictions, and the reachability of internal services from the application host.

Exploit preconditions

  • Attack surface: The WikiPageWebService.download() service operation or an interface that exposes it
  • Required access: Ability to reach and invoke the affected functionality; authentication requirements depend on deployment configuration
  • Trigger point: Processing a download request containing attacker-influenced network destination data
  • Why exploitation is possible: The server performs an outbound request without sufficiently restricting which destinations or network schemes may be contacted

Why this happens

The underlying bug is an insufficient separation between user-controlled destination data and trusted outbound network operations. When application code accepts a caller-influenced URL or network location and uses it for server-side retrieval without robust destination validation, an attacker may redirect the server toward internal, loopback, link-local, or otherwise unintended resources. This behavior maps to CWE-918: Server-Side Request Forgery.

Potential impact

  • The server may access internal services that are not publicly reachable
  • Attackers could retrieve sensitive responses or service metadata
  • Internal administrative interfaces may be exposed to unauthorized requests
  • Cloud instance metadata or credentials could potentially be accessed
  • The application may be used as a pivot for network reconnaissance or lateral movement

General mitigation guidance

Mitigation generally focuses on reducing trust in caller-supplied destinations and constraining all server-side outbound requests.

Common defensive patterns include:

  • Allowing downloads only from an explicit, narrowly defined destination allowlist
  • Validating schemes, hostnames, ports, DNS results, and redirect targets
  • Rechecking resolved addresses to prevent loopback, private, link-local, and reserved-network access
  • Disabling or restricting redirects and unsupported network protocols
  • Applying outbound firewall and egress policies at the host, container, or network layer
  • Separating download functionality from sensitive internal network segments
  • Running the service with minimal network and filesystem privileges
  • Returning only the intended resource and avoiding unnecessary response details

How teams detect issues like this

Detection approaches commonly include:

  • Static analysis for outbound HTTP or URL-fetching operations that consume request-controlled values
  • Code review checks for missing scheme, hostname, port, redirect, and private-address validation
  • Dynamic testing with controlled internal, loopback, link-local, and redirect destinations
  • Network monitoring for unexpected application connections to internal services or metadata endpoints
  • Policy enforcement requiring approved egress destinations for server-side download features
  • Automated security review tools that identify SSRF-prone data flows

Sources

SourceLink
github.comgithub.com/fangtang7/CVE/blob/main/Zyplayer-Doc/Zyplayer-Doc.md

Frequently asked

questions

It may be remotely exploitable when the affected download operation is reachable through a network interface and accepts attacker-influenced destination data. Actual exposure depends on authentication, authorization, and deployment controls.

An attacker generally needs access to invoke the affected service operation. If the operation is protected, valid credentials or another authorized application context may be required.

Restrict outbound requests to an explicit allowlist, validate destinations after DNS resolution, limit redirects and protocols, and enforce network-level egress controls as defense in depth.

Treat all request-supplied URLs as untrusted, centralize outbound request validation, review server-side fetch features, and continuously monitor application egress traffic.

Find out what's already
exploitable in your codebase.