CVE-2026-46697 HIGH

CVE-2026-46697: Fediverse Embeds: Unauthenticated SSRF / open proxy via REST media-proxy endpoint

Vendor Stefanbohacek
Product fediverse-embeds-wordpress-plugin
Weakness CWE-918 · SSRF
Published June 11, 2026
Last update June 11, 2026

CVSS base score

7.5/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity None

CVSS vector

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

What the vulnerability does

01Description

Fediverse Embeds embeds fediverse posts on WordPress sites. Prior to version 1.5.8, Fediverse Embeds registered an unauthenticated REST route ftf/media-proxy (includes/Media_Proxy.php) with permission_callback => __return_true that accepted a base64-encoded URL and forwarded it to wp_remote_get($url) without enforcing any allowlist. The plugin's source contained a comment block explicitly acknowledging that the request should be validated against allowed fediverse domains, but in 1.5.7 the validation only set a local $can_download_media flag that was never read. The full response body was echoed back to the caller, so this was a full-read SSRF / open proxy reachable by any anonymous visitor. This issue has been patched in version 1.5.8.

Explanation of Vulnerability in Simple Terms

02Summary

The Fediverse Embeds WordPress plugin before version 1.5.8 contains a server-side request forgery vulnerability. An attacker can make the plugin send HTTP requests to internal or external systems on behalf of the site. No authentication is required. This could expose internal services, leak sensitive data, or be used to attack other systems.

What an attacker can do

03Attacker Capabilities

Make the site send HTTP requests to internal or external systems without authorization.

Potential impact on your site

04Site Impact

Attackers can probe your internal network, access internal services, or use your site to attack other systems.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required.

Key dates

06Disclosure timeline

June 11, 2026 CVE published
June 11, 2026 Record updated