# CVE-2024-0768: Envo's Elementor Templates & Widgets for WooCommerce <= 1.4.4 - Cross-Site Request Forgery via ajax_theme_activation

> Unauthenticated attackers can trick administrators into activating arbitrary themes via CSRF, requiring user interaction to exploit.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-j6c9-6p46-r4qr

## What is CVE-2024-0768?

CVE-2024-0768 is a medium-severity vulnerability in envothemes Envo's Templates & Widgets for Elementor and WooCommerce, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Envo's Elementor Templates & Widgets for WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to and including 1.4.4. This is due to missing or incorrect nonce validation on the ajax_theme_activation function. This makes it possible for unauthenticated attackers to activate arbitrary installed themes via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-0768?

It affects 1 product.


Products: Envothemes Envo\'s Elementor Templates \& Widgets for Woocommerce.

## How do I fix CVE-2024-0768?

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

## Is CVE-2024-0768 being exploited?

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

## Other vulnerabilities in envothemes Envo's Templates & Widgets for Elementor and WooCommerce

- [CVE-2024-50447](https://insights.sbomify.com/CVE-2024-50447/): Cross-site scripting in Envo's Elementor Templates & Widgets for WooCommerce (medium 6.5)
- [CVE-2024-35167](https://insights.sbomify.com/CVE-2024-35167/): Cross-site scripting in Envo's Elementor Templates & Widgets for WooCommerce (medium 6.5)
- [CVE-2024-43292](https://insights.sbomify.com/CVE-2024-43292/): Cross-site scripting in Envo's Elementor Templates & Widgets for WooCommerce (medium 5.9)
- [CVE-2024-0766](https://insights.sbomify.com/CVE-2024-0766/): Envo's Elementor Templates & Widgets for WooCommerce <= 1.4.4 - Missing Authorization via templates_ajax_request (medium 4.3)
- [CVE-2024-0767](https://insights.sbomify.com/CVE-2024-0767/): Envo's Elementor Templates & Widgets for WooCommerce <= 1.4.4 - Cross-Site Request Forgery via ajax_plugin_activation (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0768 and fix it if it is affected.

What it is: CVE-2024-0768 is a medium-severity vulnerability in envothemes Envo's Templates & Widgets for Elementor and WooCommerce, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-0768 in the wild and no public exploit code.

Affected product: envothemes Envo's Templates & Widgets for Elementor and WooCommerce. 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-2024-0768/ (Markdown: https://insights.sbomify.com/CVE-2024-0768/index.md)
```

## Sources

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

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