WPBakery Plugin CSRF and XSS in Template Import

The Export & Import WPBakery Page Builder WordPress plugin through 1.0.2 does not perform any CSRF check on its template-import feature and does not sanitise the imported data before storing it and echoing it back, allowing attackers to make a logged-in administrator import a crafted template via a forged request that results in Stored Cross-Site Scripting executed in the administrator's session.

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 Export & Import WPBakery Page Builder plugin through version 1.0.2 contains a critical vulnerability that combines CSRF (Cross-Site Request Forgery) and Stored XSS (Cross-Site Scripting) in its template import functionality. This vulnerability allows attackers to trick administrators into importing malicious templates through forged requests, which then execute arbitrary JavaScript in the admin's browser session. WordPress site administrators running this plugin are directly at risk, as the attack requires no user interaction beyond visiting a malicious page while logged into WordPress. The vulnerability is particularly dangerous because it affects privileged administrator accounts, potentially leading to site compromise, malware injection, or credential theft.

Casky's 323 matching security skills leverage Claude's extended reasoning to detect the attack patterns underlying this CVE across the Initial Access (TA0001) and Persistence (TA0043) MITRE ATT&CK phases. Practitioners using the platform would identify findings related to: (1) unvalidated CSRF tokens in state-changing operations, flagging the absence of nonce verification on the template-import endpoint; (2) improper input sanitization patterns where user-supplied template data flows directly into storage and output without escaping; (3) behavioral signals of Stored XSS post-exploitation, such as unauthorized script injection in post/page content; and (4) suspicious admin-level requests originating from external referrers. The AI-driven analysis would surface these detection gaps alongside remediation guidance specific to WordPress plugin hardening, enabling teams to prioritize patch deployment and validate whether their versions are affected before active exploitation occurs.

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-81429.

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-81429

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

Run the skill that detects this →

X Instagram LinkedIn