CVE-2025-7526
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to arbitrary file deletion (via renaming) due to insufficient file path validation in the set_user_profile_image function in all versions up to, and including, 6.6.7. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Travel Engine WordPress plugin has an unauthenticated arbitrary file deletion vulnerability in the set_user_profile_image function due to insufficient path validation. Attackers can specify any file path for deletion via renaming, and deleting wp-config.php allows trivial remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate WP Travel Engine plugin installation directoryCheck if the directory wp-content/plugins/wp-travel-engine/ exists on the WordPress server filesystemAffected if The plugin directory does not exist - the plugin is not installed and is not affected
-
Identify installed plugin versionOpen the main plugin file (typically wp-travel-engine.php) and locate the version comment in the plugin header, or check the readme.txt file for the 'Stable tag' entryAffected if Version number cannot be determined or is below 6.6.8 - the installed version is vulnerable
-
Confirm plugin activation statusQuery the WordPress database option table for the active_plugins option, or check via WordPress admin dashboard under Plugins > Installed PluginsAffected if WP Travel Engine appears in the list of active plugins - the vulnerable code is accessible to unauthenticated users
You are affected if WP Travel Engine plugin is installed, active, and the installed version is below 6.6.8 - the unauthenticated arbitrary file deletion vulnerability is present
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate to version 6.6.8 or later immediately. If patching is not possible, consider disabling the plugin until an update is available.
WP Travel Engine version 6.6.8 or latest
- Backup your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find WP Travel Engine plugin and update to version 6.6.8 or the latest available version
- Verify the update was successful by checking the plugin version number
- Confirm the site still functions correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7526 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data