CVE-2025-4965: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in WPBakery Page Builder for WordPress
The WPBakery Page Builder for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Grid Builder feature in all versions up to, and including, 8.4.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
AI Analysis
Technical Summary
CVE-2025-4965 is a stored cross-site scripting (XSS) vulnerability identified in the WPBakery Page Builder plugin for WordPress, specifically within its Grid Builder feature. The vulnerability exists due to improper neutralization of input during web page generation, classified under CWE-79. It affects all versions up to and including 8.4.1. The root cause is insufficient sanitization and escaping of user-supplied attributes, which allows authenticated users with author-level privileges or higher to inject arbitrary JavaScript code into pages. When other users access these pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, defacement, or distribution of malware. The vulnerability requires no user interaction beyond page access but does require authenticated access with author-level permissions, limiting exploitation to insiders or compromised accounts. The CVSS v3.1 score of 6.4 reflects a medium severity with network attack vector, low attack complexity, and partial impact on confidentiality and integrity but no impact on availability. No public exploits have been reported yet, but the widespread use of WPBakery Page Builder in WordPress sites increases the potential attack surface. The vulnerability highlights the importance of proper input validation and output encoding in web applications, especially in plugins that allow user-generated content or attributes.
Potential Impact
The impact of CVE-2025-4965 is primarily on the confidentiality and integrity of affected websites and their users. Successful exploitation allows an attacker with author-level access to inject malicious scripts that execute in the context of the victim's browser. This can lead to theft of session cookies, enabling account takeover, unauthorized actions performed on behalf of users, defacement of website content, or distribution of malware. While availability is not directly affected, the reputational damage and potential data breaches can have significant business consequences. Organizations relying on WPBakery Page Builder may face increased risk of insider threats or compromised author accounts being leveraged for attacks. The vulnerability could also be used as a foothold for further attacks within a compromised WordPress environment. Given the plugin's popularity, a large number of websites globally are at risk, especially those with multiple authors or contributors. The medium severity rating suggests moderate urgency but should not be underestimated due to the potential for chained attacks and data exposure.
Mitigation Recommendations
To mitigate CVE-2025-4965, organizations should take the following specific actions: 1) Immediately update WPBakery Page Builder to a patched version once available; monitor vendor advisories for patches. 2) Restrict author-level access strictly to trusted users and review user roles regularly to minimize the number of users who can exploit this vulnerability. 3) Implement Web Application Firewall (WAF) rules to detect and block suspicious script injection attempts targeting the Grid Builder feature. 4) Conduct thorough input validation and output encoding on all user-supplied data within custom code or additional plugins interacting with WPBakery. 5) Monitor website logs and user activity for unusual behavior indicative of exploitation attempts. 6) Educate content authors about the risks of injecting untrusted content and enforce content submission policies. 7) Consider disabling or limiting the use of the Grid Builder feature if immediate patching is not feasible. 8) Regularly back up website data and have an incident response plan ready to address potential compromises. These steps go beyond generic advice by focusing on access control, monitoring, and proactive defense tailored to the vulnerability's exploitation vector.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, India, Brazil, France, Netherlands, Japan, Italy, Spain
CVE-2025-4965: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in WPBakery Page Builder for WordPress
Description
The WPBakery Page Builder for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Grid Builder feature in all versions up to, and including, 8.4.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-4965 is a stored cross-site scripting (XSS) vulnerability identified in the WPBakery Page Builder plugin for WordPress, specifically within its Grid Builder feature. The vulnerability exists due to improper neutralization of input during web page generation, classified under CWE-79. It affects all versions up to and including 8.4.1. The root cause is insufficient sanitization and escaping of user-supplied attributes, which allows authenticated users with author-level privileges or higher to inject arbitrary JavaScript code into pages. When other users access these pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, defacement, or distribution of malware. The vulnerability requires no user interaction beyond page access but does require authenticated access with author-level permissions, limiting exploitation to insiders or compromised accounts. The CVSS v3.1 score of 6.4 reflects a medium severity with network attack vector, low attack complexity, and partial impact on confidentiality and integrity but no impact on availability. No public exploits have been reported yet, but the widespread use of WPBakery Page Builder in WordPress sites increases the potential attack surface. The vulnerability highlights the importance of proper input validation and output encoding in web applications, especially in plugins that allow user-generated content or attributes.
Potential Impact
The impact of CVE-2025-4965 is primarily on the confidentiality and integrity of affected websites and their users. Successful exploitation allows an attacker with author-level access to inject malicious scripts that execute in the context of the victim's browser. This can lead to theft of session cookies, enabling account takeover, unauthorized actions performed on behalf of users, defacement of website content, or distribution of malware. While availability is not directly affected, the reputational damage and potential data breaches can have significant business consequences. Organizations relying on WPBakery Page Builder may face increased risk of insider threats or compromised author accounts being leveraged for attacks. The vulnerability could also be used as a foothold for further attacks within a compromised WordPress environment. Given the plugin's popularity, a large number of websites globally are at risk, especially those with multiple authors or contributors. The medium severity rating suggests moderate urgency but should not be underestimated due to the potential for chained attacks and data exposure.
Mitigation Recommendations
To mitigate CVE-2025-4965, organizations should take the following specific actions: 1) Immediately update WPBakery Page Builder to a patched version once available; monitor vendor advisories for patches. 2) Restrict author-level access strictly to trusted users and review user roles regularly to minimize the number of users who can exploit this vulnerability. 3) Implement Web Application Firewall (WAF) rules to detect and block suspicious script injection attempts targeting the Grid Builder feature. 4) Conduct thorough input validation and output encoding on all user-supplied data within custom code or additional plugins interacting with WPBakery. 5) Monitor website logs and user activity for unusual behavior indicative of exploitation attempts. 6) Educate content authors about the risks of injecting untrusted content and enforce content submission policies. 7) Consider disabling or limiting the use of the Grid Builder feature if immediate patching is not feasible. 8) Regularly back up website data and have an incident response plan ready to address potential compromises. These steps go beyond generic advice by focusing on access control, monitoring, and proactive defense tailored to the vulnerability's exploitation vector.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-05-19T20:20:43.214Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6853b5d433c7acc04608c993
Added to database: 6/19/2025, 7:01:40 AM
Last enriched: 2/27/2026, 2:55:54 PM
Last updated: 3/26/2026, 11:12:07 AM
Views: 200
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.