# CVE-2024-1684: Otter Blocks PRO <= 2.6.3 - Authenticated(Contributor+) Stored Cross-Site Scripting via File Field CSS

> Authenticated attackers with contributor access can inject arbitrary web scripts via the contact form file field CSS metabox in the Otter Blocks PRO plugin.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gr37-6cx4-ch8m

## What is CVE-2024-1684?

CVE-2024-1684 is a medium-severity cross-site scripting vulnerability in Themisle Otter Blocks PRO – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE, published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the contact form file field CSS metabox in all versions up to, and including, 2.6.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-1684?

It affects 1 product.


Products: Themeisle Otter Blocks.

## How do I fix CVE-2024-1684?

No fix has been published for CVE-2024-1684 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-1684 being exploited?

There is no known exploitation of CVE-2024-1684 in the wild and no public exploit code.

## Other vulnerabilities in Themisle Otter Blocks PRO – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE

- [CVE-2024-3725](https://insights.sbomify.com/CVE-2024-3725/): Cross-site scripting in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE (medium 6.4)
- [CVE-2024-3343](https://insights.sbomify.com/CVE-2024-3343/): Cross-site scripting in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE (medium 6.4)
- [CVE-2024-3344](https://insights.sbomify.com/CVE-2024-3344/): Cross-site scripting in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE (medium 6.4)
- [CVE-2024-2226](https://insights.sbomify.com/CVE-2024-2226/): Cross-site scripting in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE (medium 6.4)
- [CVE-2024-2841](https://insights.sbomify.com/CVE-2024-2841/): Cross-site scripting in Otter Blocks – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1684 and fix it if it is affected.

What it is: CVE-2024-1684 is a medium-severity cross-site scripting vulnerability in Themisle Otter Blocks PRO – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE, published on 13 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1684 in the wild and no public exploit code.

Affected product: Themisle Otter Blocks PRO – Gutenberg Blocks, Page Builder for Gutenberg Editor & FSE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1684/ (Markdown: https://insights.sbomify.com/CVE-2024-1684/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1684
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1684
- OSV: https://osv.dev/vulnerability/CVE-2024-1684

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1684/
Summaries are generated and may contain mistakes; the official description above is the record.