# CVE-2026-45214: WordPress Xpro Elementor Addons plugin <= 1.5.1 - SQL Injection vulnerability

> Attackers can perform blind SQL injection to read sensitive database information from the Xpro Elementor Addons plugin.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **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:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-h67w-h28r-2hgc

## What is CVE-2026-45214?

CVE-2026-45214 is a high-severity SQL injection vulnerability in Xpro Elementor Addons, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Xpro Xpro Elementor Addons xpro-elementor-addons allows Blind SQL Injection.This issue affects Xpro Elementor Addons: from n/a through <= 1.5.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-45214?


## How do I fix CVE-2026-45214?

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

## Is CVE-2026-45214 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45214 and fix it if it is affected.

What it is: CVE-2026-45214 is a high-severity SQL injection vulnerability in Xpro Elementor Addons, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45214 in the wild and no public exploit code.

Affected product: Xpro Elementor Addons. 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-2026-45214/ (Markdown: https://insights.sbomify.com/CVE-2026-45214/index.md)
```

## Sources

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

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