WP Travel Gutenberg Blocks
wp-travel-blocks · plugin
Known security vulnerabilities for WP Travel Gutenberg Blocks. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
1 critical · 2 exploitable without logging in · latest Jun 17, 2026
Listed on wordpress.org · latest 3.9.8 · last updated Jul 28, 2026 · 800+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.3
CVE-2026-54808unauthenticated≤ 3.9.4
WordPress WP Travel Gutenberg Blocks plugin <= 3.9.4 - SQL Injection vulnerability
- High 8.1
CVE-2025-53207unauthenticated≤ 3.9.0
WordPress WP Travel Gutenberg Blocks plugin <= 3.9.0 - Local File Inclusion Vulnerability
- Medium 6.5
CVE-2025-62063login required≤ 3.9.2
WordPress WP Travel Gutenberg Blocks plugin <= 3.9.2 - Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2024-47627login required≤ 3.6.0
WordPress WP Travel Gutenberg Blocks plugin <= 3.6.0 - Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2024-43284login required≤ 3.5.1
WordPress WP Travel Gutenberg Blocks plugin <= 3.5.1 - Cross Site Scripting (XSS) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).