CVE-2024-3107

Spectra – WordPress Gutenberg Blocks <= 2.12.6 - Authenticated (Contributor+) Path Traversal

2024-04-26 00:00
Ngô Thiên An (ancorn_)

Strategic Overview

Status
Patched in 2.12.7
Affected Plugin
Spectra Legacy – Gutenberg Blocks
Affected Version
<= 2.12.6
CVSS
4.3Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2024-3107
View all Spectra Legacy – Gutenberg Blocks vulnerabilities

At a glance

CVE-2024-3107 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Spectra Legacy WordPress plugin, affecting versions <= 2.12.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.12.7; sites on affected versions should update now. Disclosed April 2024, reported by Ngô Thiên An (ancorn_).

Vulnerability Overview

The Spectra – WordPress Gutenberg Blocks plugin for WordPress is vulnerable to Path Traversal in versions up to, and including, 2.12.6 via the get_block_default_attributes function. This allows authenticated attackers, with contributor-level permissions and above, to read the contents of any files named attributes.php on the server, which can contain sensitive information.

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-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Spectra Legacy <= 2.12.6 takes an account at Contributor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Spectra Legacy the fix is 2.12.7: builds <= 2.12.6 are affected, anything from 2.12.7 onward is not.

Remediation

Update to version 2.12.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.12.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-3107https://www.wordfence.com/threat-intel/vulnerabilities/id/110e5e67-b318-4ab2-9b4d-59aabcf7db7chttps://nvd.nist.gov/vuln/detail/CVE-2024-3107

Related records

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