# CVE-2024-58349: WordPress Theme Travelscape 1.0.3 Arbitrary File Upload

> Unauthenticated attackers can upload malicious files to the Travelscape theme to achieve remote code execution on the WordPress site.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-976h-hgxf-4vrc

## What is CVE-2024-58349?

CVE-2024-58349 is a critical vulnerability in WP Travel Kit Travelscape, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress Theme Travelscape 1.0.3 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious files by exploiting insufficient validation in the theme's upload functionality. Attackers can upload arbitrary files to the theme directory and execute them to achieve remote code execution on the affected WordPress installation.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-58349 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-58349 is a critical vulnerability in WP Travel Kit Travelscape, published on 8 Jun 2026. 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-2024-58349 exists.

Affected product: WP Travel Kit Travelscape. 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-58349/ (Markdown: https://insights.sbomify.com/CVE-2024-58349/index.md)
```

## Sources

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

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