# CVE-2024-54256: WordPress Easy Blocks pro plugin <= 1.0.21 - Broken Access Control vulnerability

> Attackers can access restricted functionality in the Easy Blocks pro WordPress plugin due to missing authorization checks.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **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 Dec 2024
- **Updated:** 12 May 2026
- **Also known as:** GHSA-gv5w-pqg2-3w8x

## What is CVE-2024-54256?

CVE-2024-54256 is a high-severity missing authorization vulnerability in Seerox Easy Blocks pro, published on 13 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Seerox Easy Blocks pro easy-blocks-pro allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Easy Blocks pro: from n/a through <= 1.0.21.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-54256 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54256 is a high-severity missing authorization vulnerability in Seerox Easy Blocks pro, published on 13 Dec 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-54256 in the wild and no public exploit code.

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

## Sources

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

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