# CVE-2025-0968: ElementsKit Elementor addons <= 3.4.0 - Unauthenticated Information Exposure via get_megamenu_content Function

> Unauthenticated attackers can view private, draft, and trashed Elementor content due to missing capability checks in the ElementsKit plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8528-jjpw-q9wx

## What is CVE-2025-0968?

CVE-2025-0968 is a medium-severity missing authorization vulnerability in roxnor ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ElementsKit Elementor addons plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.4.0  due to a missing capability checks on the get_megamenu_content() function. This makes it possible for unauthenticated attackers to view any item created in Elementor, such as posts, pages and templates including drafts, trashed and private items.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-0968?

It affects 1 product.


Products: Wpmet Elementskit Elementor Addons.

## How do I fix CVE-2025-0968?

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

## Is CVE-2025-0968 being exploited?

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

## Other vulnerabilities in roxnor ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor

- [CVE-2025-3614](https://insights.sbomify.com/CVE-2025-3614/): Cross-site scripting in ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor (medium 6.4)
- [CVE-2025-4479](https://insights.sbomify.com/CVE-2025-4479/): ElementsKit Lite <= 3.5.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Image Comparison Widget (medium 6.4)
- [CVE-2024-11180](https://insights.sbomify.com/CVE-2024-11180/): ElementsKit Elementor addons <= 3.4.7 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)
- [CVE-2025-1005](https://insights.sbomify.com/CVE-2025-1005/): Cross-site scripting in ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor (medium 6.4)
- [CVE-2024-8546](https://insights.sbomify.com/CVE-2024-8546/): ElementsKit Elementor addons <= 3.2.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via Video Widget (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0968 and fix it if it is affected.

What it is: CVE-2025-0968 is a medium-severity missing authorization vulnerability in roxnor ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor, published on 19 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0968 in the wild and no public exploit code.

Affected product: roxnor ElementsKit Elementor Addons – Advanced Widgets & Templates 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-2025-0968/ (Markdown: https://insights.sbomify.com/CVE-2025-0968/index.md)
```

## Sources

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

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