WPBakery template import CSRF stores attacker scripts
Export & Import WPBakery Page Builder through 1.0.2 performs no CSRF check on template import and stores and echoes imported data without sanitization. A forged request can make a logged-in administrator import a crafted template whose JavaScript later executes in the administrator's session. The authoritative export does not name the action, import field, or render context.
- Component
- Export & Import WPBakery Page Builder
- Plugin slug
export-import-wpbakery-page-builder- Affected
- <= 1.0.2
- Safe version
- See mitigation notes
- Published
- Sep 12, 2026
This CVE was published Sep 12, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
No fixed release is confirmed in the authoritative export. Deactivate the plugin and remove untrusted imported templates. The application-level fix must require a nonce and appropriate capability, sanitize the imported schema, and escape every stored value for its output context.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L