Skip to main content
Vulnerability Database/CVE-2026-96039

CVE-2026-96039: BA Book Everything WordPress Plugin XSS Flaw

CVE-2026-96039 is a stored XSS vulnerability in the BA Book Everything WordPress plugin affecting versions up to 1.8.27. Unauthenticated attackers can inject malicious scripts via the first_name parameter. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-96039 Overview

CVE-2026-96039 is a stored Cross-Site Scripting (XSS) vulnerability in the BA Book Everything plugin for WordPress. The flaw affects all versions up to and including 1.8.27 and stems from insufficient input sanitization and output escaping of the first_name parameter. Unauthenticated attackers can inject arbitrary web scripts that execute whenever a user visits an affected page.

The exploit chain requires valid order_id, order_num, and order_hash values to reach the vulnerable action_to_pay() handler. Attackers can obtain these credentials by placing a guest booking through the public [babe-booking-form] shortcode, making the full chain reachable without authentication.

Critical Impact

Unauthenticated attackers can inject persistent JavaScript into booking pages, enabling session theft, administrative account takeover, and arbitrary actions in the context of visiting users including site administrators.

Affected Products

  • BA Book Everything plugin for WordPress — all versions through 1.8.27
  • WordPress sites exposing the [babe-booking-form] shortcode publicly
  • Any WordPress deployment using the vulnerable action_to_pay() handler path

Discovery Timeline

  • 2026-09-25 - CVE-2026-96039 published to the National Vulnerability Database
  • 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-96039

Vulnerability Analysis

The vulnerability is a stored XSS flaw classified under [CWE-79]. User-supplied data from the first_name parameter is persisted to the database and later rendered in page output without proper sanitization or escaping. When an administrator or another user loads the resulting booking page, the injected script executes in that user's browser context.

The vulnerable code path lives in the plugin's order handling logic, with references across class-babe-order.php (lines 2405, 2522, 2599, 2653) and class-babe-html.php (line 4300). The action_to_pay() handler renders the stored first_name value into HTML output without applying esc_html(), esc_attr(), or an equivalent context-aware escaping function.

Root Cause

The root cause is a failure to apply WordPress's standard sanitization APIs on input (such as sanitize_text_field()) and context-appropriate escaping on output. The first_name field accepts arbitrary characters, including HTML tags and <script> elements, which are then written back to the DOM verbatim when the payment page is rendered.

Attack Vector

An unauthenticated attacker submits a guest booking through the public [babe-booking-form] shortcode, placing an XSS payload in the first_name field. The booking submission returns the order_id, order_num, and order_hash values needed to reach action_to_pay(). The attacker then shares the crafted payment URL, or waits for an administrator to review the booking in the backend. When the page renders, the stored payload executes in the visitor's browser. Review the vulnerable source at the WordPress BA Book HTML Class and the WordPress BA Book Order Class for context.

Detection Methods for CVE-2026-96039

Indicators of Compromise

  • Booking records in the plugin's order tables containing <script>, onerror=, onload=, or javascript: payloads in the first_name column
  • Unexpected outbound requests from administrator browsers immediately after viewing booking or payment pages
  • Newly created WordPress administrator accounts or modified user roles following access to a booking payment page
  • Access log entries showing POST requests to the booking endpoint from unauthenticated clients with unusual first_name values

Detection Strategies

  • Scan the plugin's order storage for HTML or JavaScript syntax in guest-provided name fields using database queries
  • Deploy a Web Application Firewall rule to flag booking form submissions containing <, >, or javascript: within the first_name parameter
  • Monitor WordPress audit logs for administrator sessions that trigger script execution events in the browser's content security policy reports

Monitoring Recommendations

  • Enable Content Security Policy (CSP) reporting on WordPress admin pages to detect inline script execution attempts
  • Correlate guest booking creation events with subsequent administrator views of the payment page URL
  • Alert on changes to WordPress user roles, option values, or plugin configuration occurring within minutes of booking page access

How to Mitigate CVE-2026-96039

Immediate Actions Required

  • Update the BA Book Everything plugin to the version released in WordPress Update Changeset 3709588 which supersedes 1.8.27
  • Audit existing booking records for malicious payloads in the first_name field and purge affected entries
  • Rotate administrator credentials and invalidate active sessions if the plugin was exposed before patching

Patch Information

The vendor addressed the issue in a release that applies proper sanitization and escaping on the first_name parameter. Technical details of the fix are documented in the Wordfence Vulnerability Analysis DD118053 and the corresponding WordPress plugin repository changeset.

Workarounds

  • Temporarily remove the [babe-booking-form] shortcode from all public pages until the patch is applied
  • Deploy a WAF rule rejecting booking submissions where first_name contains HTML special characters such as <, >, or "
  • Restrict access to the WordPress admin area with IP allowlisting to limit which users render stored booking data
bash
# Example WAF rule (ModSecurity) blocking XSS payloads in first_name
SecRule ARGS:first_name "@rx (?i)(<script|onerror=|onload=|javascript:)" \
    "id:1026960039,phase:2,deny,status:403,msg:'Blocked XSS attempt in BA Book Everything first_name parameter'"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.