# CVE-2026-106648: Royal Elementor Addons < 1.7.1070 - Unauthenticated Arbitrary Email Recipient Injection via Form Field ID Shortcodes


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-qc47-xccv-ch2q

## What is CVE-2026-106648?

CVE-2026-106648 is a medium-severity vulnerability in Unknown Royal Elementor Addons, published on 28 Oct 2026. 

### Official description

The Royal Elementor Addons WordPress plugin before 1.7.1070 does not validate submitted form field values before substituting them into the recipient addresses of its form notification emails, allowing unauthenticated attackers to replace the recipient list and relay attacker-composed email from the site's own domain when a recipient field is configured to echo a submitted value.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-106648 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106648 is a medium-severity vulnerability in Unknown Royal Elementor Addons, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-106648 in the wild and no public exploit code.

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

## Sources

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

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