Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 3.0.6 - Unauthetnicated Path Traversal to Arbitrary Image View
Strategic Overview
- Status
- Patched in 3.0.7
- Affected Version
<= 3.0.6- CVSS
- 5.3Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2024-11219
At a glance
CVE-2024-11219 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Otter Blocks WordPress plugin, affecting versions <= 3.0.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.7; sites on affected versions should update now. Disclosed November 2024, reported by mikemyers.
Vulnerability Overview
The Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 3.0.6 via the get_image function. This makes it possible for unauthenticated attackers to view arbitrary images 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 privileges on the target site, and no interaction from a victim user.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Otter Blocks <= 3.0.6 takes a caller who can reach the endpoint. 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 Otter Blocks the fix is 3.0.7: builds <= 3.0.6 are affected, anything from 3.0.7 onward is not.
Remediation
Update to version 3.0.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Otter Blocks: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Otter Blocks 3.0.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE
- 8.8CVE-2023-2288: Otter - Gutenberg Blocks <= 2.2.5 PHAR Deserialization
CVE-2023-2288 - 7.5CVE-2026-2892: Otter Blocks Improper Authorization
CVE-2026-2892 - 6.4CVE-2024-10367: Otter Blocks Stored XSS
CVE-2024-10367 - 6.4CVE-2024-3725: Otter Blocks Stored XSS
CVE-2024-3725 - 6.4CVE-2024-3343: Otter Blocks Stored XSS
CVE-2024-3343 - 6.4CVE-2024-3344: Otter Blocks Limited File Upload to Stored XSS
CVE-2024-3344 - 6.4CVE-2024-2841: Otter Blocks Stored XSS
CVE-2024-2841 - 6.4CVE-2024-2729: Otter Blocks <= 2.6.5 Stored Cross-Site Scripting
CVE-2024-2729
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C