Comparison Overview
Back-Roads Touring

Back-Roads Touring
109 Power Road, None, London, England, GB, W4 5
Last Update: 05/12/2025
With almost 40 years of experience, we’re confident you’ll experience every destination’s deepest layer on our expertly crafted small-group tours... At Back-Roads Touring, we invite you to join us on a journey of discovery. Together, we’ll amble through the narrow pas...

BCD Travel
Europalaan 300, Utrecht, NL, 3526 KS
Last Update: 04/06/2026
BCD Travel helps companies travel smart and achieve more. We drive program adoption, cost savings and talent retention through digital experiences that simplify business travel. Our 15,000+ dedicated team members service clients in 170+ countries as we shape a sustainab...
Compliance Ranges Comparison

Back-Roads Touring







BCD Travel






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Back-Roads Touring in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
BCD Travel has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Back-Roads Touring (X = Date, Y = Severity)
Back-Roads Touring cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BCD Travel (X = Date, Y = Severity)
BCD Travel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Back-Roads Touring

BCD Travel
FAQ
Latest Global CVEs
phpMyFAQ before 4.1.5 contains a privilege escalation vulnerability in GroupController::updatePermissions that allows GROUP_EDIT administrators to grant arbitrary rights to groups without verifying they hold those rights themselves. A delegated administrator can exploit this by assigning high-value permissions to a group they belong to, inheriting those rights and escalating privileges up to full administrative control.
n8n before 2.25.7 and 2.26.x before 2.26.2 contains an abstract syntax tree (AST) security validator bypass in the Python Code node. An authenticated user with permission to create or modify workflows containing a Python Code node can bypass the validator and access the task executor module namespace. The issue only affects self-hosted instances where the Python Task Runner is enabled; where N8N_BLOCK_RUNNER_ENV_ACCESS is configured to allow it, this can disclose environment variables accessible to the task runner process.
Grav CMS before 2.0.0-beta.2 contains multiple code-execution vulnerabilities. Three unsafe unserialize() calls - in Scheduler\JobQueue, Framework\Cache\Adapter\FileCache, and Session - deserialize untrusted data without restricting allowed classes, enabling PHP object injection and, via a gadget chain, arbitrary code execution where an attacker controls the serialized input. Additionally, InstallCommand's git clone operation passes the branch, url, and path parameters into a shell command without escaping, allowing OS command injection via plugin/theme installation (which requires admin access). A Twig security blocklist bypass (server-side template injection) is also present. The issues are fixed in 2.0.0-beta.2.
Storage Concentrator (SC & SCVM) contains a command injection vulnerability within the debug.pl script that is reachable without authentication. A remote attacker can submit a specially crafted HTTP request containing a malicious payload that is processed without adequate input sanitization, resulting in arbitrary command execution with root-level privileges on the underlying system.
Storage Concentrator (SC & SCVM) contains a command injection vulnerability in the ms_service.pl service, which listens on TCP port 9000 by default and accepts custom network packets to perform device actions. An unauthenticated remote attacker can send a specially crafted packet containing a malicious payload that is processed without adequate sanitization, resulting in arbitrary command execution with root-level privileges.