Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE <= 3.0.4 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload
Strategic Overview
- Status
- Patched in 3.0.5
- Affected Version
<= 3.0.4- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2024-10367
At a glance
CVE-2024-10367 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Otter Blocks WordPress plugin, affecting versions <= 3.0.4. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 3.0.5; sites on affected versions should update now. Disclosed October 2024, reported by Francesco Carlucci.
Vulnerability Overview
The Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REST API SVG File uploads in all versions up to, and including, 3.0.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.
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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Otter Blocks <= 3.0.4 takes an account at Author level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Otter Blocks the fix is 3.0.5: builds <= 3.0.4 are affected, anything from 3.0.5 onward is not.
Remediation
Update to version 3.0.5, or a newer patched version
How does WordSec protect against this?
An attacker needs Author 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: Otter Blocks 3.0.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
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-3344: Otter Blocks Limited File Upload to Stored XSS
CVE-2024-3344 - 6.4CVE-2024-2226: Otter Blocks Stored XSS
CVE-2024-2226 - 5.3CVE-2026-4945: Otter Blocks Unauthenticated Purchase Verification
CVE-2026-4945 - 5.3CVE-2025-55715: Otter - Gutenberg Block <= 3.1.0 Info Exposure
CVE-2025-55715 - 5.3CVE-2024-11219: Otter Blocks Unauthetnicated Path Traversal
CVE-2024-11219 - 5.3CVE-2024-1047: ThemeIsle SDK <= Various Versions Missing Authorization
CVE-2024-1047
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C