CVE-2024-13591: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in labibahmed42 Team Builder For WPBakery Page Builder(Formerly Visual Composer)
CVE-2024-13591 is a stored cross-site scripting (XSS) vulnerability in the Team Builder For WPBakery Page Builder WordPress plugin, affecting all versions up to 1. 0. It arises from improper input sanitization and output escaping in the 'team-builder-vc' shortcode, allowing authenticated users with contributor-level or higher privileges to inject malicious scripts. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or further attacks. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction but does require authentication with limited privileges. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or applying mitigations to prevent exploitation, especially in environments with multiple contributors. Countries with significant WordPress usage and large web publishing sectors are most at risk.
AI Analysis
Technical Summary
CVE-2024-13591 is a stored cross-site scripting vulnerability identified in the Team Builder For WPBakery Page Builder plugin for WordPress, formerly known as Visual Composer. The vulnerability stems from insufficient sanitization and escaping of user-supplied attributes within the plugin's 'team-builder-vc' shortcode. Specifically, authenticated users with contributor-level access or higher can inject arbitrary JavaScript code into pages via this shortcode. Because the injected scripts are stored persistently, they execute every time any user accesses the affected page, leading to potential compromise of user sessions, theft of sensitive information, or unauthorized actions performed on behalf of users. The vulnerability affects all versions up to and including 1.0 of the plugin. The CVSS v3.1 base score is 6.4, reflecting a medium severity level, with an attack vector of network, low attack complexity, requiring privileges (contributor or higher), no user interaction, and a scope change. The impact includes limited confidentiality and integrity loss but no availability impact. No patches or official fixes are currently linked, and no active exploitation has been reported. The vulnerability highlights the risks of improper input validation in WordPress plugins, especially those that allow user-generated content or shortcode attributes. Attackers exploiting this flaw could leverage it to escalate privileges or conduct phishing and session hijacking attacks within affected sites.
Potential Impact
The primary impact of CVE-2024-13591 is the compromise of confidentiality and integrity within affected WordPress sites. Attackers with contributor-level access can inject malicious scripts that execute in the context of other users, including administrators, potentially leading to session hijacking, credential theft, or unauthorized actions such as content manipulation or privilege escalation. This can undermine trust in the affected website, cause data breaches, and facilitate further attacks like malware distribution or phishing. Since the vulnerability requires authenticated access, the risk is somewhat limited to environments where multiple users have contributor or higher roles. However, many WordPress sites have broad contributor access, increasing exposure. The vulnerability does not affect availability directly but can result in reputational damage and operational disruption. Organizations relying on this plugin for team or staff presentation features may face defacement or data leakage. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as exploit code could be developed rapidly once public. Overall, the vulnerability poses a moderate risk to organizations using the affected plugin, particularly those with multiple content contributors and high-value targets such as media, education, and corporate websites.
Mitigation Recommendations
To mitigate CVE-2024-13591, organizations should first check for updates or patches from the plugin vendor and apply them promptly once available. In the absence of official patches, administrators should consider disabling or removing the Team Builder For WPBakery Page Builder plugin if it is not essential. Restrict contributor-level access strictly to trusted users and review user roles to minimize the number of users who can exploit this vulnerability. Implement a Web Application Firewall (WAF) with custom rules to detect and block suspicious shortcode attribute inputs containing script tags or event handlers. Conduct regular security audits and scanning of WordPress sites to detect injected scripts or anomalous content. Educate content contributors about the risks of injecting untrusted content and enforce strict content validation policies. Additionally, consider using security plugins that provide enhanced input sanitization and output escaping for shortcodes. Monitor logs for unusual activity indicative of exploitation attempts. Finally, maintain regular backups to enable recovery in case of compromise.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, India, France, Netherlands, Brazil, Japan
CVE-2024-13591: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in labibahmed42 Team Builder For WPBakery Page Builder(Formerly Visual Composer)
Description
CVE-2024-13591 is a stored cross-site scripting (XSS) vulnerability in the Team Builder For WPBakery Page Builder WordPress plugin, affecting all versions up to 1. 0. It arises from improper input sanitization and output escaping in the 'team-builder-vc' shortcode, allowing authenticated users with contributor-level or higher privileges to inject malicious scripts. These scripts execute whenever any user views the compromised page, potentially leading to session hijacking, defacement, or further attacks. The vulnerability has a CVSS score of 6. 4 (medium severity) and does not require user interaction but does require authentication with limited privileges. No known exploits are currently reported in the wild. Organizations using this plugin should prioritize patching or applying mitigations to prevent exploitation, especially in environments with multiple contributors. Countries with significant WordPress usage and large web publishing sectors are most at risk.
AI-Powered Analysis
Technical Analysis
CVE-2024-13591 is a stored cross-site scripting vulnerability identified in the Team Builder For WPBakery Page Builder plugin for WordPress, formerly known as Visual Composer. The vulnerability stems from insufficient sanitization and escaping of user-supplied attributes within the plugin's 'team-builder-vc' shortcode. Specifically, authenticated users with contributor-level access or higher can inject arbitrary JavaScript code into pages via this shortcode. Because the injected scripts are stored persistently, they execute every time any user accesses the affected page, leading to potential compromise of user sessions, theft of sensitive information, or unauthorized actions performed on behalf of users. The vulnerability affects all versions up to and including 1.0 of the plugin. The CVSS v3.1 base score is 6.4, reflecting a medium severity level, with an attack vector of network, low attack complexity, requiring privileges (contributor or higher), no user interaction, and a scope change. The impact includes limited confidentiality and integrity loss but no availability impact. No patches or official fixes are currently linked, and no active exploitation has been reported. The vulnerability highlights the risks of improper input validation in WordPress plugins, especially those that allow user-generated content or shortcode attributes. Attackers exploiting this flaw could leverage it to escalate privileges or conduct phishing and session hijacking attacks within affected sites.
Potential Impact
The primary impact of CVE-2024-13591 is the compromise of confidentiality and integrity within affected WordPress sites. Attackers with contributor-level access can inject malicious scripts that execute in the context of other users, including administrators, potentially leading to session hijacking, credential theft, or unauthorized actions such as content manipulation or privilege escalation. This can undermine trust in the affected website, cause data breaches, and facilitate further attacks like malware distribution or phishing. Since the vulnerability requires authenticated access, the risk is somewhat limited to environments where multiple users have contributor or higher roles. However, many WordPress sites have broad contributor access, increasing exposure. The vulnerability does not affect availability directly but can result in reputational damage and operational disruption. Organizations relying on this plugin for team or staff presentation features may face defacement or data leakage. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as exploit code could be developed rapidly once public. Overall, the vulnerability poses a moderate risk to organizations using the affected plugin, particularly those with multiple content contributors and high-value targets such as media, education, and corporate websites.
Mitigation Recommendations
To mitigate CVE-2024-13591, organizations should first check for updates or patches from the plugin vendor and apply them promptly once available. In the absence of official patches, administrators should consider disabling or removing the Team Builder For WPBakery Page Builder plugin if it is not essential. Restrict contributor-level access strictly to trusted users and review user roles to minimize the number of users who can exploit this vulnerability. Implement a Web Application Firewall (WAF) with custom rules to detect and block suspicious shortcode attribute inputs containing script tags or event handlers. Conduct regular security audits and scanning of WordPress sites to detect injected scripts or anomalous content. Educate content contributors about the risks of injecting untrusted content and enforce strict content validation policies. Additionally, consider using security plugins that provide enhanced input sanitization and output escaping for shortcodes. Monitor logs for unusual activity indicative of exploitation attempts. Finally, maintain regular backups to enable recovery in case of compromise.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-01-21T15:05:23.090Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6e61b7ef31ef0b59f4b7
Added to database: 2/25/2026, 9:49:21 PM
Last enriched: 2/25/2026, 11:29:21 PM
Last updated: 2/26/2026, 8:22:37 AM
Views: 3
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-1698: CWE-644 Improper Neutralization of HTTP Headers for Scripting Syntax in arcinfo PcVue
MediumCVE-2026-1697: CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in arcinfo PcVue
MediumCVE-2026-1696: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in arcinfo PcVue
LowCVE-2026-1695: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in arcinfo PcVue
MediumCVE-2026-1694: CWE-201 Insertion of Sensitive Information into Sent Data in arcinfo PcVue
LowActions
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.