Quick answers
- Is CVE-2026-81429 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81429 being exploited in the wild.
- How severe is CVE-2026-81429?
- High severity, with a CVSS score of 7.1, published 12 September 2026.
- Which products and versions are affected?
- WPBakery Export & Import WPBakery Page Builder through 1.0.2.
- Is there a fix for CVE-2026-81429?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81429 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81429?
- Check whether you run WPBakery Export & Import WPBakery Page Builder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The plugin fails to implement CSRF tokens on its template-import endpoint and does not sanitize or escape imported data before storing and displaying it. An attacker can craft a malicious template file containing JavaScript payloads and trick an authenticated administrator into importing it via a cross-site request (e.g., through a crafted webpage). The unsanitized data is then stored in the database and executed in the administrator's session when the template is viewed or managed. This is a stored XSS vulnerability requiring admin-level access to trigger, with no known patch available as of the advisory date.
Affected products
- WPBakery Export & Import WPBakery Page Builder through 1.0.2
Timeline
- 2026-09-10: disclosed
- 2026-09-12: advisory