CVE-2025-69390
Reflected XSS in Business Template Blocks for WPBakery
Publication date: 2026-02-20
Last updated on: 2026-02-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| themebon | business_template_blocks_for_wpbakery_visual_composer_page_builder | From 1.0.0 (inc) to 1.3.2 (inc) |
| themebon | business_template_blocks_for_wpbakery_page_builder | to 1.3.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-69390 is a medium severity Cross Site Scripting (XSS) vulnerability affecting the WordPress Business Template Blocks for WPBakery (Visual Composer) Page Builder Plugin versions up to and including 1.3.2.
This vulnerability allows an attacker to inject malicious scriptsβsuch as redirects, advertisements, or other HTML payloadsβinto a website, which execute when visitors access the compromised pages.
Exploitation requires user interaction by a privileged user who must perform an action like clicking a malicious link, visiting a crafted page, or submitting a form.
Although the vulnerability can be initiated by an unauthenticated user, successful exploitation depends on this privileged user action.
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'This vulnerability can impact you by allowing attackers to execute malicious scripts on your website, which can lead to unauthorized redirects, display of unwanted advertisements, or execution of harmful HTML payloads.'}, {'type': 'paragraph', 'content': 'Such attacks can compromise the integrity and trustworthiness of your website, potentially harming your users and damaging your reputation.'}, {'type': 'paragraph', 'content': "Since exploitation requires a privileged user to interact with malicious content, it can also lead to unauthorized actions performed under that user's credentials."}, {'type': 'paragraph', 'content': 'No official patch is currently available, but mitigation rules exist to block attacks targeting this vulnerability.'}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a Reflected Cross Site Scripting (XSS) issue in the Business Template Blocks for WPBakery Page Builder plugin. Detection typically involves monitoring for unusual or malicious script injections in web page requests and responses.
Since the vulnerability requires user interaction such as clicking a malicious link or submitting a crafted form, detection can include analyzing web server logs for suspicious query parameters or payloads that contain script tags or encoded JavaScript.
Specific commands are not provided in the available resources, but common approaches include using tools like curl or wget to test for reflected script injection by sending crafted requests to the affected endpoints and observing the responses.
- Use curl to send a test request with a script payload in URL parameters and check if the script is reflected in the response.
- Analyze web server access logs for suspicious query strings containing script tags or encoded payloads.
- Use web vulnerability scanners that support XSS detection against the affected plugin endpoints.
What immediate steps should I take to mitigate this vulnerability?
There is currently no official patch available for this vulnerability in the Business Template Blocks for WPBakery Page Builder plugin up to version 1.3.2.
Immediate mitigation involves applying the Patchstack mitigation rule that can block attacks targeting this flaw until an official patch is released.
Users are strongly advised to implement this mitigation immediately to protect their websites from exploitation.
Additionally, limiting user interactions that could trigger the vulnerability, such as restricting access to privileged users or educating users about phishing risks, can help reduce exploitation chances.