# CVE-2024-1330: Kadence Blocks Pro < 2.3.8 - Contributor+ Arbitrary Option Access

> Contributors can leak arbitrary database options via shortcode functionalities in the Kadence Blocks Pro WordPress plugin.

- **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:** 27 Jun 2024
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-8qj9-f5hw-7wqq

## What is CVE-2024-1330?

CVE-2024-1330 is a medium-severity vulnerability in Unknown kadence-blocks-pro, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The kadence-blocks-pro WordPress plugin before 2.3.8 does not prevent users with at least the contributor role using some of its shortcode's functionalities to leak arbitrary options from the database.

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

It affects 1 product.


Products: Kadencewp Kadence Blocks Pro.

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

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

## Is CVE-2024-1330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1330 is a medium-severity vulnerability in Unknown kadence-blocks-pro, published on 27 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-1330 in the wild and no public exploit code.

Affected product: Unknown kadence-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-1330/ (Markdown: https://insights.sbomify.com/CVE-2024-1330/index.md)
```

## Sources

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

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