CVE-2026-49770
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 · uneditedUnauthenticated PHP Object Injection in WP Travel Engine <= 6.7.12 versions.
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 · moderate confidenceUnauthenticated PHP Object Injection vulnerability in the WP Travel Engine WordPress plugin (versions <= 6.7.12). This critical flaw allows remote attackers to inject malicious PHP objects without authentication, potentially leading to remote code execution depending on available gadget chains within the application.
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 filesCheck the wp-content/plugins/ directory for a folder named 'wp-travel-engine' or access the plugin page in WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the WordPress plugins directory
-
Determine installed plugin versionAccess Plugins > Installed Plugins in WordPress admin and find WP Travel Engine, or open the main plugin file (usually wp-travel-engine/wp-travel-engine.php) and look for the 'Version:' header in the plugin commentsAffected if The displayed version number is 6.7.12 or lower
-
Verify vulnerability scope is reachedThis is an unauthenticated vulnerability affecting the plugin core functionality - no specific feature or setting needs to be enabled for exploitationAffected if The plugin is installed and active with a version of 6.7.12 or lower
You are affected if the WP Travel Engine plugin is installed with any version numbered 6.7.12 or below, as this allows unauthenticated PHP object injection.
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 WP Travel Engine to a version newer than 6.7.12 immediately. If immediate updating is not possible, disable the plugin or implement WAF rules to block exploitation attempts.
WP Travel Engine 6.7.13 or later
- 1. Backup your WordPress site and database before making any changes.
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
- 3. Find WP Travel Engine in the plugin list.
- 4. If an update is available, click 'Update Now' to update to the latest version.
- 5. Alternatively, you can manually download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin.
- 6. Verify the update was successful by checking the plugin version after updating.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49770 — 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-2026-49770 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