# CVE-2026-10834: WP Travel Engine < 6.8.1 - Subscriber+ Arbitrary Media File Move via user_profile_image

> Authenticated subscribers can move arbitrary files within the WordPress uploads directory, potentially breaking site content.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-qj2j-73pj-4fxf

## What is CVE-2026-10834?

CVE-2026-10834 is a medium-severity path traversal vulnerability in Unknown WP Travel Engine, published on 7 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The WP Travel Engine  WordPress plugin before 6.8.1 does not properly validate the source of a user-supplied profile image path before moving the file, allowing authenticated users with subscriber-level access and above to relocate arbitrary files within the WordPress uploads directory into their own profile-image path. This removes the targeted media from its original location and can break content across the site.

## Which versions are affected by CVE-2026-10834?


## How do I fix CVE-2026-10834?

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

## Is CVE-2026-10834 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10834 and fix it if it is affected.

What it is: CVE-2026-10834 is a medium-severity path traversal vulnerability in Unknown WP Travel Engine, published on 7 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10834 exists.

Affected product: Unknown WP Travel Engine. 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-2026-10834/ (Markdown: https://insights.sbomify.com/CVE-2026-10834/index.md)
```

## Sources

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

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