# CVE-2024-35682: WordPress Otter Blocks PRO plugin <= 2.6.11 - Authenticated Sensitive Data Exposure vulnerability

> Authenticated attackers can access sensitive information in the Otter Blocks PRO WordPress plugin, requiring an upgrade to mitigate.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 8 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-49mm-8468-22hq

## What is CVE-2024-35682?

CVE-2024-35682 is a medium-severity vulnerability in Themeisle Otter Blocks PRO, published on 8 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Themeisle Otter Blocks PRO.This issue affects Otter Blocks PRO: from n/a through 2.6.11.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Themeisle Otter Blocks.

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

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

## Is CVE-2024-35682 being exploited?

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

## Other vulnerabilities in Themeisle Otter Blocks PRO

- [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-35682 and fix it if it is affected.

What it is: CVE-2024-35682 is a medium-severity vulnerability in Themeisle Otter Blocks PRO, published on 8 Jun 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-35682 in the wild and no public exploit code.

Affected product: Themeisle Otter Blocks PRO. 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-35682/ (Markdown: https://insights.sbomify.com/CVE-2024-35682/index.md)
```

## Sources

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

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