Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-59552

CVE-2026-59552: 3D Flipbook PDF Viewer SSRF Vulnerability

CVE-2026-59552 is an unauthenticated Server-Side Request Forgery vulnerability in 3D Flipbook PDF Viewer & Embedder plugin that enables attackers to make unauthorized server requests. Learn about affected versions, impact, and mitigation.

Published:

CVE-2026-59552 Overview

CVE-2026-59552 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the 3D Flipbook PDF Viewer & Embedder WordPress plugin, affecting versions up to and including 1.4.2. The flaw allows remote attackers to coerce the vulnerable WordPress server into issuing arbitrary HTTP requests to attacker-chosen destinations without any authentication. Successful exploitation can expose internal network services, cloud metadata endpoints, and other resources reachable from the WordPress host. The vulnerability is classified under CWE-918: Server-Side Request Forgery.

Critical Impact

Unauthenticated attackers can pivot through the WordPress server to reach internal-only services, potentially exposing cloud instance metadata, internal APIs, and non-public assets.

Affected Products

  • 3D Flipbook PDF Viewer & Embedder WordPress plugin versions <= 1.4.2
  • WordPress installations with the pdf-embed-viewer plugin enabled
  • Hosting environments where the WordPress server has access to internal networks or cloud metadata services

Discovery Timeline

  • 2026-07-27 - CVE-2026-59552 published to NVD
  • 2026-07-27 - Last updated in NVD database

Technical Details for CVE-2026-59552

Vulnerability Analysis

The vulnerability exists in the 3D Flipbook PDF Viewer & Embedder plugin, which accepts a user-controlled URL parameter used to fetch and render PDF content server-side. Because the plugin does not validate or restrict the destination of outbound requests, an attacker can direct the server to request arbitrary URLs. The endpoint requires no authentication, so any unauthenticated remote user can trigger the request.

SSRF vulnerabilities in WordPress plugins are commonly used to reach cloud metadata endpoints such as http://169.254.169.254/, internal administrative interfaces, and services bound to loopback addresses. Attackers may also use the flaw to scan internal networks by observing response timing or content differences. Refer to the Patchstack SSRF Vulnerability Report for the vendor advisory.

Root Cause

The root cause is missing validation of a URL parameter passed to the plugin's PDF-fetching functionality. The plugin does not enforce an allow-list of remote hosts, does not block private and link-local IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16), and does not restrict URL schemes. This falls under [CWE-918].

Attack Vector

An unauthenticated attacker sends a crafted HTTP request to the vulnerable plugin endpoint with a URL parameter pointing to an internal target. The WordPress server issues an outbound request to that URL and, depending on the response handling, may return content, headers, or error data to the attacker. This can enable reconnaissance of internal services, exfiltration of cloud IAM credentials from metadata endpoints, and interaction with internal APIs that trust requests from the WordPress host.

No verified public exploit code is available for this CVE. See the Patchstack advisory linked above for additional technical detail.

Detection Methods for CVE-2026-59552

Indicators of Compromise

  • Outbound HTTP requests from the WordPress server to internal RFC1918 addresses, 127.0.0.1, or 169.254.169.254
  • Access log entries for the 3D Flipbook plugin endpoint containing URL parameters pointing to non-PDF or internal resources
  • Unexpected DNS resolutions initiated by the WordPress PHP process for attacker-controlled or internal domains
  • Anomalous outbound requests from the web server to cloud metadata service endpoints

Detection Strategies

  • Monitor web server access logs for requests to the pdf-embed-viewer plugin paths with suspicious URL query parameters
  • Alert on any outbound connection from the WordPress host to 169.254.169.254 or other cloud metadata IPs
  • Baseline normal outbound destinations for the WordPress server and flag deviations to internal address space
  • Inspect PHP process network activity for connections to non-standard ports on internal hosts

Monitoring Recommendations

  • Enable egress logging and DNS query logging on the WordPress host to capture SSRF probe activity
  • Forward WordPress access logs and host network telemetry to a central analytics platform for correlation
  • Configure alerts for repeated 4xx/5xx responses tied to the plugin endpoint, which can indicate scanning attempts
  • Review cloud audit logs for API calls originating from instance credentials that align with SSRF exploitation timing

How to Mitigate CVE-2026-59552

Immediate Actions Required

  • Update the 3D Flipbook PDF Viewer & Embedder plugin to a version above 1.4.2 once a fixed release is available from the vendor
  • Disable or remove the pdf-embed-viewer plugin on all WordPress sites until a patch is applied
  • Enforce Instance Metadata Service v2 (IMDSv2) on AWS instances hosting WordPress to block classic SSRF against the metadata endpoint
  • Audit outbound traffic from WordPress hosts for prior connections to internal services or metadata endpoints

Patch Information

Consult the Patchstack advisory for the latest fix status. As of the NVD publication on 2026-07-27, all versions <= 1.4.2 are affected.

Workarounds

  • Block outbound requests from the WordPress host to RFC1918 ranges and 169.254.169.254 at the network firewall or cloud security group level
  • Deploy a WAF rule to inspect and reject requests to plugin endpoints that carry URL parameters referencing internal or non-HTTP schemes
  • Restrict the WordPress server's egress to an allow-list of legitimate external destinations required for operation
  • Rotate any cloud IAM credentials associated with the affected instance if SSRF activity is observed in logs
bash
# Example egress restriction using iptables to block cloud metadata access
iptables -A OUTPUT -d 169.254.169.254 -j DROP
iptables -A OUTPUT -d 10.0.0.0/8 -p tcp -j DROP
iptables -A OUTPUT -d 172.16.0.0/12 -p tcp -j DROP
iptables -A OUTPUT -d 192.168.0.0/16 -p tcp -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.