# CVE-2022-3805: Jeg Elementor Kit <= 2.5.6 - Unauthenticated Authorization Bypass

> Unauthenticated attackers can bypass authorization to modify plugin settings, including API keys and styles, by exploiting a predictable nonce in Jeg Elementor Kit.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-j26m-pwx8-x5jf

## What is CVE-2022-3805?

CVE-2022-3805 is a high-severity missing authorization vulnerability in jegtheme Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress, published on 22 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Jeg Elementor Kit plugin for WordPress is vulnerable to authorization bypass in various functions used to update the plugin settings in versions up to, and including, 2.5.6. Unauthenticated users can use an easily available nonce, obtained from pages edited by the plugin, to update the MailChimp API key, global styles, 404 page settings, and enabled elements.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2022-3805?

It affects 1 product.


Products: Jegtheme Jeg Elementor Kit.

## How do I fix CVE-2022-3805?

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

## Is CVE-2022-3805 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3805 exists.

Public exploit code:

- Jeg Elementor Kit < 2.5.7 - Unauthenticated Settings Update (nuclei): http/cves/2022/CVE-2022-3805.yaml

## Other vulnerabilities in jegtheme Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress

- [CVE-2024-47390](https://insights.sbomify.com/CVE-2024-47390/): WordPress Jeg Elementor Kit plugin <= 2.6.8 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-32721](https://insights.sbomify.com/CVE-2024-32721/): WordPress Jeg Elementor Kit plugin <= 2.6.3 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-29101](https://insights.sbomify.com/CVE-2024-29101/): WordPress Jeg Elementor Kit plugin <= 2.6.2 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-10308](https://insights.sbomify.com/CVE-2024-10308/): Jeg Elementor Kit <= 2.6.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via JKit - Countdown Widget (medium 6.4)
- [CVE-2024-6804](https://insights.sbomify.com/CVE-2024-6804/): Jeg Elementor Kit <= 2.6.7 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3805 and fix it if it is affected.

What it is: CVE-2022-3805 is a high-severity missing authorization vulnerability in jegtheme Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress, published on 22 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3805 exists.

Affected product: jegtheme Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress. 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-2022-3805/ (Markdown: https://insights.sbomify.com/CVE-2022-3805/index.md)
```

## Sources

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

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