Export & Import WPBakery Page Builder WordPress: cross-site scripting (XSS)
Export & Import WPBakery Page Builder WordPress
Cross-site scripting (XSS) in the Export & Import WPBakery Page Builder WordPress component. Threat level: High (CVSS 7.1).
Who is affected
This vulnerability affects: Export & Import WPBakery Page Builder WordPress. If you use this component on your site, check the version and update it as soon as possible.
How dangerous
Rating: High, CVSS 7.1 out of 10. It is worth acting before the flaw is exploited.
What this flaw is
Cross-site scripting (XSS) lets an attacker inject foreign JavaScript into the page, which runs in the browser of a visitor or a logged-in administrator.
The attacker can hijack the session, replace content, or steal data from forms. "Stored" variants are more dangerous, because the code is saved permanently and hits everyone who opens the infected page.
Score breakdown (CVSS vector)
What the CVSS 7.1 rating means in practice:
- The attack can be carried out remotely, over the internet.
- No login or account required.
- Requires user action (e.g. clicking a link).
- The impact may reach beyond the vulnerable component itself.
- At risk: data confidentiality, integrity (data can be altered), site availability.
Weakness class: CWE-79.
How to fix: cross-site scripting (XSS)
- Update the component to the version that fixes the flaw.
- Check posts, comments and options for injected <script> tags or unknown external scripts, and clear the page/CDN cache.
- Add a Content-Security-Policy header to limit what scripts can run.
- If administrator sessions may have been hijacked, force a re-login and rotate passwords.
Prefer not to do this yourself? We will handle the update, check for signs of a break-in and secure the site. Write to us →
Frequently asked questions
Does this vulnerability affect my site?
It affects sites that use Export & Import WPBakery Page Builder WordPress. Check whether you have this component installed and which version, the flaw only applies to the vulnerable version range. You can verify it in under a minute with our free vulnerability scanner.
How do I check whether I have the vulnerable version?
In your admin panel (in WordPress: Plugins / Themes) check the installed version of Export & Import WPBakery Page Builder WordPress and compare it with the vendor advisory that names the fixed version. If it is lower, or you are not sure, run our scanner, which reads the versions visible in the site code.
How urgently should I react?
This is a Wysoka-severity flaw, so treat it as urgent, high-impact vulnerabilities are often exploited automatically within hours of disclosure. Update as soon as possible.
What if a patch is not available yet?
Until a fix ships, reduce the exposure: temporarily disable the vulnerable component, restrict access to the affected functionality, or add a WAF rule blocking the vulnerable request. Keep a current off-site backup and watch for signs of a break-in.
Is updating alone enough?
If the site has not been attacked yet, updating to the patched version closes the hole. If there are already signs of compromise (unknown files, new admin accounts, redirects), the update does not undo the break-in, you also need to clean the site and rotate passwords and the WordPress salts.
Does this flaw affect your site?
We will run a free audit: we check versions, plugins, and configuration, and tell you plainly whether you are safe.
Request a free audit →