WordPress Bit Integrations Plugin Stored XSS Flaw

The Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'field mapped to notification_content (attacker-chosen key, e.g. payload_text)' parameter in all versions up to, and including, 2.10.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires a site administrator to have preconfigured a Bit Integrations flow that binds the public Bit Assist webhook to a BuddyBoss "Send Notification" action with a form field mapped to notification_content, and the attacker to know the flow's UUID callback URL.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Bit integrations plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability affecting all versions up to 2.10.6. Attackers can inject malicious JavaScript through improperly sanitized notification content fields, which then executes whenever users access affected pages. This vulnerability is particularly dangerous because it requires no authentication and persists in the database, meaning every site visitor becomes a potential victim. Given the plugin's popularity for form handling, webhooks, and CRM integrations, this flaw exposes thousands of WordPress installations to account compromise, credential theft, and malware distribution.

Casky's 323 matched security skills leverage Claude AI with extended reasoning to detect the attack patterns underlying this vulnerability across both Initial Access (TA0001) and Persistence (TA0043) techniques. Practitioners using Casky would observe detection patterns focused on: (1) payload injection detection in notification field parameters, identifying characteristic XSS encoding attempts and script tag variations; (2) output encoding verification gaps in WordPress plugin sanitization workflows; and (3) stored payload activation monitoring that flags when injected scripts execute on page load. Practitioners would see findings highlighting dangerous parameter chains—such as user input flowing from form submissions directly into notification_content without proper escaping—and receive actionable guidance on implementing parameterized output encoding and content security policy headers to neutralize stored XSS threats before they propagate across user sessions.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-102007.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-102007

Casky has 323 skills that investigate the attack patterns behind CVE-2026-102007. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn