CVE-2026-66704

Gutenverse Companion <= 2.5.1 - Unauthenticated Server-Side Request Forgery

2026-08-10 00:00
Ananda Dhakal

Strategic Overview

Status
Patched in 2.5.2
Affected Plugin
Gutenverse Companion
Affected Version
<= 2.5.1
CVSS
7.2High
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-66704
View all Gutenverse Companion vulnerabilities

At a glance

CVE-2026-66704 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Gutenverse Companion WordPress plugin, affecting versions <= 2.5.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.2; sites on affected versions should update now. Disclosed August 2026, reported by Ananda Dhakal.

Vulnerability Overview

The Gutenverse Companion plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 2.5.1. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Gutenverse Companion <= 2.5.1 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Gutenverse Companion the fix is 2.5.2: builds <= 2.5.1 are affected, anything from 2.5.2 onward is not.

Remediation

Update to version 2.5.2, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Gutenverse Companion 2.5.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C