# CVE-2024-12045: Cross-site scripting in Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns

> Administrators can inject arbitrary scripts via Google Maps block titles in WordPress, affecting multi-site or restricted HTML configurations.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2025
- **Updated:** 20 May 2026
- **Also known as:** GHSA-wgq3-vq6c-fvpp

## What is CVE-2024-12045?

CVE-2024-12045 is a medium-severity cross-site scripting vulnerability in wpdevteam Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns, published on 8 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Essential Blocks – Page Builder Gutenberg Blocks, Patterns & Templates plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the maker title value of the Google Maps block  in all versions up to, and including, 5.0.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

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

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

It affects 1 product.


Products: Wpdeveloper Essential Blocks.

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

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

## Is CVE-2024-12045 being exploited?

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

## Other vulnerabilities in wpdevteam Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns

- [CVE-2023-6623](https://insights.sbomify.com/CVE-2023-6623/): Essential Blocks < 4.4.3 - Unauthenticated Local File Inclusion (critical 9.8)
- [CVE-2023-4386](https://insights.sbomify.com/CVE-2023-4386/): Essential Blocks <= 4.2.0 - Unauthenticated PHP Object Injection via queries (high 8.1)
- [CVE-2023-4402](https://insights.sbomify.com/CVE-2023-4402/): Essential Blocks <= 4.2.0 - Unauthenticated PHP Object Injection via products (high 8.1)
- [CVE-2022-47594](https://insights.sbomify.com/CVE-2022-47594/): WordPress Essential Blocks for Gutenberg plugin <= 3.8.5 - Broken Access Control (medium 6.5)
- [CVE-2023-51360](https://insights.sbomify.com/CVE-2023-51360/): WordPress Essential Blocks plugin <= 4.2.0 - Multiple Subscriber+ Broken Access Control vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12045 is a medium-severity cross-site scripting vulnerability in wpdevteam Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns, published on 8 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12045 in the wild and no public exploit code.

Affected product: wpdevteam Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns. 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-12045/ (Markdown: https://insights.sbomify.com/CVE-2024-12045/index.md)
```

## Sources

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

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