CVE-2024-3667: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in themefusecom Brizy – Page Builder
CVE-2024-3667 is a high-severity Stored Cross-Site Scripting (XSS) vulnerability in the Brizy – Page Builder WordPress plugin, affecting all versions up to 2. 4. 43. The flaw arises from insufficient input sanitization and output escaping in the 'Link To' field of multiple widgets, allowing authenticated users with contributor-level access or higher to inject malicious scripts. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or further exploitation. Exploitation does not require user interaction beyond page access, and the vulnerability impacts confidentiality, integrity, and availability. No public exploits are currently known, but the vulnerability's nature and ease of exploitation make it a significant risk for WordPress sites using this plugin. Immediate patching or mitigation is recommended to prevent abuse.
AI Analysis
Technical Summary
CVE-2024-3667 is a Stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, found in the Brizy – Page Builder plugin for WordPress developed by themefusecom. This vulnerability affects all versions up to and including 2.4.43. The root cause is insufficient sanitization and escaping of user-supplied input in the 'Link To' field of multiple widgets, which allows authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript code into pages. Because the malicious script is stored persistently in the page content, it executes automatically whenever any user accesses the infected page, without requiring further interaction. The vulnerability has a CVSS 3.1 base score of 7.4, reflecting its high severity, with an attack vector of network, low attack complexity, requiring privileges (authenticated contributor or above), no user interaction, and scope change. The impact includes partial loss of confidentiality, integrity, and availability, as attackers can steal session tokens, deface content, or perform actions on behalf of other users. Although no known exploits are currently reported in the wild, the vulnerability poses a significant threat to WordPress sites using this plugin, especially those with multiple contributors. The vulnerability was publicly disclosed on June 5, 2024, and no official patches have been linked yet, emphasizing the need for immediate mitigation.
Potential Impact
The impact of CVE-2024-3667 is substantial for organizations running WordPress sites with the Brizy – Page Builder plugin. Successful exploitation allows an attacker with contributor-level access to inject persistent malicious scripts, which execute in the context of any user viewing the compromised page. This can lead to session hijacking, unauthorized actions performed on behalf of users, defacement, and potential spread of malware or phishing content. The compromise of user sessions can escalate privileges or lead to data theft, impacting confidentiality and integrity. Availability may also be affected if injected scripts disrupt site functionality or cause crashes. Given WordPress’s widespread use globally, especially in small to medium businesses, blogs, and e-commerce, this vulnerability can facilitate targeted attacks or broad exploitation campaigns. The requirement for authenticated access limits exploitation to insiders or compromised accounts, but the low complexity and lack of user interaction needed increase risk. Organizations may face reputational damage, regulatory penalties, and operational disruption if exploited.
Mitigation Recommendations
To mitigate CVE-2024-3667, organizations should first check for and apply any official patches or updates from the Brizy – Page Builder plugin vendor as soon as they become available. Until patches are released, administrators should restrict contributor-level access to trusted users only and audit existing contributor accounts for suspicious activity. Implementing a Web Application Firewall (WAF) with custom rules to detect and block suspicious input patterns in the 'Link To' field can help prevent exploitation attempts. Site administrators should also enable Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. Regularly scanning the site for injected scripts or unusual content in pages and widgets is critical to detect and remediate infections early. Additionally, educating contributors about safe input practices and monitoring logs for anomalous behavior can reduce risk. Finally, consider temporarily disabling or replacing the Brizy plugin if the risk is unacceptable and no patch is available.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, India, Brazil, Japan, Netherlands, Italy, Spain
CVE-2024-3667: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in themefusecom Brizy – Page Builder
Description
CVE-2024-3667 is a high-severity Stored Cross-Site Scripting (XSS) vulnerability in the Brizy – Page Builder WordPress plugin, affecting all versions up to 2. 4. 43. The flaw arises from insufficient input sanitization and output escaping in the 'Link To' field of multiple widgets, allowing authenticated users with contributor-level access or higher to inject malicious scripts. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or further exploitation. Exploitation does not require user interaction beyond page access, and the vulnerability impacts confidentiality, integrity, and availability. No public exploits are currently known, but the vulnerability's nature and ease of exploitation make it a significant risk for WordPress sites using this plugin. Immediate patching or mitigation is recommended to prevent abuse.
AI-Powered Analysis
Technical Analysis
CVE-2024-3667 is a Stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, found in the Brizy – Page Builder plugin for WordPress developed by themefusecom. This vulnerability affects all versions up to and including 2.4.43. The root cause is insufficient sanitization and escaping of user-supplied input in the 'Link To' field of multiple widgets, which allows authenticated users with contributor-level permissions or higher to inject arbitrary JavaScript code into pages. Because the malicious script is stored persistently in the page content, it executes automatically whenever any user accesses the infected page, without requiring further interaction. The vulnerability has a CVSS 3.1 base score of 7.4, reflecting its high severity, with an attack vector of network, low attack complexity, requiring privileges (authenticated contributor or above), no user interaction, and scope change. The impact includes partial loss of confidentiality, integrity, and availability, as attackers can steal session tokens, deface content, or perform actions on behalf of other users. Although no known exploits are currently reported in the wild, the vulnerability poses a significant threat to WordPress sites using this plugin, especially those with multiple contributors. The vulnerability was publicly disclosed on June 5, 2024, and no official patches have been linked yet, emphasizing the need for immediate mitigation.
Potential Impact
The impact of CVE-2024-3667 is substantial for organizations running WordPress sites with the Brizy – Page Builder plugin. Successful exploitation allows an attacker with contributor-level access to inject persistent malicious scripts, which execute in the context of any user viewing the compromised page. This can lead to session hijacking, unauthorized actions performed on behalf of users, defacement, and potential spread of malware or phishing content. The compromise of user sessions can escalate privileges or lead to data theft, impacting confidentiality and integrity. Availability may also be affected if injected scripts disrupt site functionality or cause crashes. Given WordPress’s widespread use globally, especially in small to medium businesses, blogs, and e-commerce, this vulnerability can facilitate targeted attacks or broad exploitation campaigns. The requirement for authenticated access limits exploitation to insiders or compromised accounts, but the low complexity and lack of user interaction needed increase risk. Organizations may face reputational damage, regulatory penalties, and operational disruption if exploited.
Mitigation Recommendations
To mitigate CVE-2024-3667, organizations should first check for and apply any official patches or updates from the Brizy – Page Builder plugin vendor as soon as they become available. Until patches are released, administrators should restrict contributor-level access to trusted users only and audit existing contributor accounts for suspicious activity. Implementing a Web Application Firewall (WAF) with custom rules to detect and block suspicious input patterns in the 'Link To' field can help prevent exploitation attempts. Site administrators should also enable Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. Regularly scanning the site for injected scripts or unusual content in pages and widgets is critical to detect and remediate infections early. Additionally, educating contributors about safe input practices and monitoring logs for anomalous behavior can reduce risk. Finally, consider temporarily disabling or replacing the Brizy plugin if the risk is unacceptable and no patch is available.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2024-04-11T18:32:49.328Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6c99b7ef31ef0b566aa9
Added to database: 2/25/2026, 9:41:45 PM
Last enriched: 2/26/2026, 6:21:36 AM
Last updated: 2/26/2026, 9:41:46 AM
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-28138: Deserialization of Untrusted Data in Stylemix uListing
HighCVE-2026-28136: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in VeronaLabs WP SMS
HighCVE-2026-28132: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in villatheme WooCommerce Photo Reviews
HighCVE-2026-28131: Insertion of Sensitive Information Into Sent Data in WPVibes Elementor Addon Elements
HighCVE-2026-28083: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in UX-themes Flatsome
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.