# CVE-2024-13353: Path traversal in Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates

> Authenticated contributors can exploit Local File Inclusion in Responsive Addons for Elementor to execute arbitrary PHP code or read sensitive data.

- **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:** 21 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r7qp-5852-gh42

## What is CVE-2024-13353?

CVE-2024-13353 is a high-severity path traversal vulnerability in cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates, published on 21 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Responsive Addons for Elementor – Free Elementor Addons Plugin and Elementor Templates plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.6.4 via several widgets. 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-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

It affects 1 product.


Products: Cyberchimps Responsive Addons for Elementor.

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

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

## Is CVE-2024-13353 being exploited?

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

## Other vulnerabilities in cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates

- [CVE-2025-54050](https://insights.sbomify.com/CVE-2025-54050/): WordPress Responsive Addons for Elementor plugin <= 1.7.3 - Cross Site Scripting (XSS) Vulnerability (medium 6.5)
- [CVE-2024-52358](https://insights.sbomify.com/CVE-2024-52358/): WordPress Responsive Addons for Elementor plugin <= 1.5.4 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2025-2225](https://insights.sbomify.com/CVE-2025-2225/): Cross-site scripting in Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates (medium 6.4)
- [CVE-2025-2228](https://insights.sbomify.com/CVE-2025-2228/): Information disclosure in Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates (medium 5.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13353 is a high-severity path traversal vulnerability in cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates, published on 21 Feb 2025. 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-13353 in the wild and no public exploit code.

Affected product: cyberchimps Responsive Addons for Elementor – Free Elementor Addons, Kits and Elementor Templates. 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-13353/ (Markdown: https://insights.sbomify.com/CVE-2024-13353/index.md)
```

## Sources

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

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