VYPR
Critical severity9.8NVD Advisory· Published Jun 15, 2026· Updated Jun 15, 2026

CVE-2026-49770

CVE-2026-49770

Description

Unauthenticated PHP Object Injection in WP Travel Engine <= 6.7.12 can lead to remote code execution or other critical impacts via a POP chain.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Unauthenticated PHP Object Injection in WP Travel Engine <= 6.7.12 can lead to remote code execution or other critical impacts via a POP chain.

Vulnerability

The WP Travel Engine plugin for WordPress, versions up to and including 6.7.12, is vulnerable to unauthenticated PHP Object Injection. An attacker can inject arbitrary serialized PHP objects via a crafted request, which may lead to remote code execution, SQL injection, path traversal, or denial of service if a suitable POP chain is present. [1]

Exploitation

No authentication is required. An attacker with network access can send a malicious HTTP request containing the serialized payload. The vulnerability is expected to be exploited in mass campaigns, targeting any site running the vulnerable plugin without any prerequisite user interaction. [1]

Impact

Successful exploitation can result in complete compromise of the affected WordPress site, including arbitrary code execution, data leakage, file manipulation, or service disruption, depending on the available POP gadgets. [1]

Mitigation

The vendor has released version 6.8.0 which fixes the vulnerability. Users should update to 6.8.0 or later immediately. For sites that cannot be updated right away, Patchstack provides a virtual patch mitigation rule to block attacks until the update is applied. [1]

AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1