<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>BA Book Everything (&lt;= 1.8.27) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/ba-book-everything--1.8.27/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 25 Sep 2026 08:55:39 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/ba-book-everything--1.8.27/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>CVE-2026-96039 Stored XSS in BA Book Everything WordPress Plugin</title><link>https://feed.craftedsignal.io/briefs/2026-09-ba-book-everything-xss/</link><pubDate>Fri, 25 Sep 2026 08:55:39 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-ba-book-everything-xss/</guid><description>The BA Book Everything WordPress plugin contains a stored XSS vulnerability in the first_name parameter, allowing unauthenticated attackers to inject arbitrary scripts.</description><content:encoded><![CDATA[<p>The BA Book Everything plugin for WordPress, versions 1.8.27 and earlier, is vulnerable to a Stored Cross-Site Scripting (XSS) attack via the first_name parameter. The vulnerability arises from insufficient input sanitization and output escaping of data submitted through the booking process. An unauthenticated attacker can exploit this by placing a guest booking via the public [babe-booking-form] shortcode, which provides the necessary parameters (order_id, order_num, order_hash) to reach the vulnerable action_to_pay() handler. Successful exploitation allows for the execution of arbitrary JavaScript in the context of a user session when they access the affected page. This vulnerability presents a significant risk for session hijacking and unauthorized data access within WordPress environments using this plugin.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker navigates to the public page containing the [babe-booking-form] shortcode.</li>
<li>Attacker initiates a guest booking flow, which generates a valid order_id, order_num, and order_hash.</li>
<li>Attacker submits the booking form while injecting a malicious payload into the first_name parameter.</li>
<li>The application processes the request, invoking the action_to_pay() handler.</li>
<li>The server stores the malicious JavaScript payload in the database without proper sanitization.</li>
<li>An administrative or other user visits the page where the stored booking information is rendered.</li>
<li>The user's browser executes the injected JavaScript payload, potentially leading to unauthorized actions or data exfiltration.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to execute arbitrary web scripts in the browser of users viewing the booking information. This can result in session hijacking, administrative account compromise, and unauthorized access to sensitive booking data, impacting any WordPress site utilizing the affected version of the BA Book Everything plugin.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the BA Book Everything plugin to a version released after 1.8.27 to mitigate CVE-2026-96039.</li>
<li>Audit access logs for high-frequency booking form submissions that include non-standard characters (like &lt;script&gt; or alert()) in the first_name field.</li>
<li>Monitor webserver access logs for POST requests to the plugin's booking handler followed by subsequent requests to the order payment or detail pages.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>