# CVE-2026-115183: Qi Addons For Elementor < 1.11.2 - Contributor+ Content Injection via Animated Text Widget


- **Severity:** Low 2.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-q3pm-872x-6qfr

## What is CVE-2026-115183?

CVE-2026-115183 is a low-severity vulnerability in Unknown Qi Addons For Elementor, published on 25 Oct 2026. 

### Official description

The Qi Addons For Elementor WordPress plugin before 1.11.2 does not properly sanitise a widget's heading text after decoding HTML entities in it, allowing users with the Contributor role and above to embed live HTML forms, including password fields that submit to an external host, into posts where WordPress would otherwise strip them.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-115183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115183 is a low-severity vulnerability in Unknown Qi Addons For Elementor, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115183 in the wild and no public exploit code.

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

## Sources

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

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