# CVE-2024-3499: ElementsKit Elementor addons <= 3.1.0 - Authenticated (Contributor+) Local File Inclusion via Onepage Scroll Module

> Authenticated contributors can exploit a local file inclusion vulnerability in the Onepage Scroll module to execute arbitrary PHP code on the server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rhf4-g6xh-53vf

## What is CVE-2024-3499?

CVE-2024-3499 is a high-severity vulnerability in roxnor ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor, published on 2 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ElementsKit Elementor addons plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.1.0 via the generate_navigation_markup function of the Onepage Scroll module. This makes it possible for authenticated attackers, with contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

It affects 1 product.


Products: Wpmet Elements Kit Elementor Addons.

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

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

## Is CVE-2024-3499 being exploited?

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

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

- [CVE-2024-2047](https://insights.sbomify.com/CVE-2024-2047/): ElementsKit Elementor addons <= 3.0.6 - Authenticated (Contributor+) Local File Inclusion in render_raw (high 8.8)
- [CVE-2024-32505](https://insights.sbomify.com/CVE-2024-32505/): WordPress ElementsKit Elementor addons plugin <= 3.0.6 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-10091](https://insights.sbomify.com/CVE-2024-10091/): Cross-site scripting in ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor (medium 6.4)
- [CVE-2024-3650](https://insights.sbomify.com/CVE-2024-3650/): Cross-site scripting in ElementsKit Elementor addons and Templates Library (medium 6.4)
- [CVE-2024-2803](https://insights.sbomify.com/CVE-2024-2803/): ElementsKit Elementor addons <= 3.0.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via Countdown Widget (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3499 is a high-severity vulnerability in roxnor ElementsKit Elementor Addons – Advanced Widgets & Templates Addons for Elementor, published on 2 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-3499 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-2024-3499/ (Markdown: https://insights.sbomify.com/CVE-2024-3499/index.md)
```

## Sources

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

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