Quick answers
- Is CVE-2026-49770 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49770 being exploited in the wild.
- How severe is CVE-2026-49770?
- Critical severity, with a CVSS score of 9.8, published 15 June 2026.
- Which products and versions are affected?
- WP Travel Engine <= 6.7.12.
- Is there a fix for CVE-2026-49770?
- A patch was published on 2026-06-04: Version 6.8.0 released to address the issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49770 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-49770?
- Check whether you run WP Travel Engine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The WP Travel Engine plugin for WordPress is vulnerable to PHP Object Injection in versions up to 6.7.12 due to improper deserialization of untrusted user input (CWE-502). An unauthenticated remote attacker can exploit this by sending a specially crafted request containing a malicious PHP object. If a suitable Property-Oriented Programming (POP) chain is present in the environment, the attacker can achieve remote code execution, perform SQL injection, or access sensitive files via path traversal. The vulnerability is resolved in version 6.8.0.
Affected products
- WP Travel Engine WP Travel Engine <= 6.7.12
Timeline
- 2026-01-15: other: Vulnerability reported by researcher daroo
- 2026-06-04: patched: Version 6.8.0 released to address the issue
- 2026-06-15: disclosed: CVE published to NVD