# CVE-2026-106647: Royal Elementor Addons 1.3.68 - 1.7.1069 - Author+ Form Submission Interception via Widget ID Collision


- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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-gv8j-xg52-fqpf

## What is CVE-2026-106647?

CVE-2026-106647 is a low-severity vulnerability in Unknown Royal Addons for Elementor, published on 28 Oct 2026. 

### Official description

The Royal Addons for Elementor  WordPress plugin before 1.7.1070 does not scope a contact form's email delivery configuration to the form's own document or owner, instead storing it in a site-global namespace keyed only on a non-secret, author-chosen identifier that is exposed in public page source, allowing users with the Author role or above to overwrite another user's form configuration and have that form's submissions delivered to an attacker-controlled address.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-106647 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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