Spectra <= 2.6.6 - Authenticated (Contributor+) Server-Side Request Forgery in template_importer

2023-07-14 00:00
Anonymous

Strategic Overview

Status
Patched in 2.6.7
Affected Plugin
Spectra Legacy – Gutenberg Blocks
Affected Version
<= 2.6.6
CVSS
6.4Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE pending
View all Spectra Legacy – Gutenberg Blocks vulnerabilities

At a glance

This record tracks a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Spectra Legacy WordPress plugin, affecting versions <= 2.6.6. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.6.7; sites on affected versions should update now. Disclosed July 2023.

Vulnerability Overview

The Spectra plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 2.6.6 via the template_importer function. This can allow authenticated attackers, with contributor-level permissions and above, to make web requests to arbitrary locations originating from the web application and 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 interaction from a victim user.

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

Reaching this weakness in Spectra Legacy <= 2.6.6 takes an account at Contributor level or above. 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 Spectra Legacy the fix is 2.6.7: builds <= 2.6.6 are affected, anything from 2.6.7 onward is not.

Remediation

Update to version 2.6.7, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Spectra Legacy 2.6.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/b139260b-7741-4e35-b23f-896f23719739

Related records

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