# CVE-2026-12500: WP Travel Engine < 6.8.2 - Unauthenticated Trip Difficulty Level Option Update

> Unauthenticated attackers can modify site-wide travel engine options due to missing capability checks on an AJAX action.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-jfwf-348v-33wp

## What is CVE-2026-12500?

CVE-2026-12500 is a high-severity missing authorization vulnerability in Unknown WP Travel Engine, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Travel Engine  WordPress plugin before 6.8.2 does not perform a capability check on an AJAX action that updates a WP Travel Engine  WordPress plugin before 6.8.2 option, allowing unauthenticated users to overwrite a site-wide WP Travel Engine  WordPress plugin before 6.8.2 option (the public nonce that gates the action is served to anonymous visitors).

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12500 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12500 is a high-severity missing authorization vulnerability in Unknown WP Travel Engine, published on 30 Jul 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-2026-12500 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-12500/ (Markdown: https://insights.sbomify.com/CVE-2026-12500/index.md)
```

## Sources

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

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