# CVE-2025-5282: WP Travel Engine <= 6.5.1 - Missing Authorization to Unauthenticated Arbitrary Post Deletion

> Unauthenticated attackers can delete arbitrary posts due to a missing capability check in the WP Travel Engine plugin.

- **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:** 13 Jun 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-jq5m-6mwv-f3j3

## What is CVE-2025-5282?

CVE-2025-5282 is a high-severity missing authorization vulnerability in wptravelengine WP Travel Engine – Tour Booking Plugin – Tour Operator Software, published on 13 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the delete_package() function in all versions up to, and including, 6.5.1. This makes it possible for unauthenticated attackers to delete arbitrary posts.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-5282?

It affects 1 product.


Products: Wptravelengine Wp Travel Engine.

## How do I fix CVE-2025-5282?

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

## Is CVE-2025-5282 being exploited?

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

## Other vulnerabilities in wptravelengine WP Travel Engine – Tour Booking Plugin – Tour Operator Software

- [CVE-2024-30502](https://insights.sbomify.com/CVE-2024-30502/): WordPress WP Travel Engine plugin <= 5.7.9 - Unauth. Blind SQL Injection vulnerability (critical 9.3)
- [CVE-2025-30870](https://insights.sbomify.com/CVE-2025-30870/): WordPress WP Travel Engine plugin <= 6.3.5 - Local File Inclusion vulnerability (high 8.1)
- [CVE-2024-30504](https://insights.sbomify.com/CVE-2024-30504/): WordPress WP Travel Engine plugin <= 5.7.9 - SQL Injection vulnerability (high 7.6)
- [CVE-2025-30871](https://insights.sbomify.com/CVE-2025-30871/): WordPress WP Travel Engine plugin <= 6.3.5 - Local File Inclusion vulnerability (high 7.5)
- [CVE-2024-32798](https://insights.sbomify.com/CVE-2024-32798/): WordPress WP Travel Engine plugin <= 5.8.0 - Price Manipulation vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5282 and fix it if it is affected.

What it is: CVE-2025-5282 is a high-severity missing authorization vulnerability in wptravelengine WP Travel Engine – Tour Booking Plugin – Tour Operator Software, published on 13 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5282 in the wild and no public exploit code.

Affected product: wptravelengine WP Travel Engine – Tour Booking Plugin – Tour Operator Software. 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-2025-5282/ (Markdown: https://insights.sbomify.com/CVE-2025-5282/index.md)
```

## Sources

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

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