CVE-2025-4669: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wpdevelop WP Booking Calendar
The WP Booking Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpbc shortcode in all versions up to, and including, 10.11.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-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
The WP Booking Calendar plugin for WordPress, widely used for managing booking functionalities on websites, contains a stored cross-site scripting vulnerability identified as CVE-2025-4669. This vulnerability stems from CWE-79, improper neutralization of input during web page generation, specifically in the handling of the wpbc shortcode. The plugin fails to adequately sanitize and escape user-supplied attributes before rendering them on pages. As a result, authenticated users with contributor-level permissions or higher can inject arbitrary JavaScript code into pages via the shortcode parameters. When other users access these pages, the malicious scripts execute in their browsers, potentially allowing attackers to steal session cookies, perform actions on behalf of users, or deface content. The vulnerability affects all versions up to and including 10.11.1. Exploitation does not require user interaction beyond page access but does require authentication with contributor or higher privileges, limiting exposure to internal or semi-trusted users. The CVSS 3.1 base score is 6.4, indicating a medium severity level, with the vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N reflecting network attack vector, low attack complexity, privileges required, no user interaction, scope change, and limited confidentiality and integrity impact without availability impact. No patches or exploits are currently publicly available, but the vulnerability poses a risk to websites relying on this plugin, especially those with multiple contributors or untrusted users. Mitigation requires updating the plugin once a fix is released or applying strict input validation and output encoding on shortcode attributes.
Potential Impact
This vulnerability can lead to unauthorized script execution in the context of affected websites, compromising user confidentiality and integrity. Attackers can hijack user sessions, steal sensitive information, or perform unauthorized actions on behalf of users, potentially leading to account compromise or data leakage. Since exploitation requires contributor-level access, the threat is primarily from insiders or compromised accounts with elevated privileges. The vulnerability does not affect system availability but can damage organizational reputation and user trust if exploited. Websites with multiple contributors or public-facing content management are at higher risk. The scope change in the CVSS vector indicates that the vulnerability can affect resources beyond the vulnerable component, increasing potential impact. Although no known exploits exist currently, the medium severity score and ease of exploitation with low complexity suggest organizations should act promptly to mitigate risk.
Mitigation Recommendations
1. Monitor for and apply official patches or updates from the wpdevelop vendor as soon as they become available to address this vulnerability. 2. Until a patch is released, restrict contributor-level access to trusted users only and review user roles to minimize unnecessary privileges. 3. Implement strict input validation and output encoding on all shortcode attributes, especially those accepting user input, to prevent script injection. 4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious shortcode payloads or script injection attempts. 5. Conduct regular security audits and code reviews of WordPress plugins and themes to identify similar vulnerabilities proactively. 6. Educate content contributors about the risks of injecting untrusted content and enforce content submission policies. 7. Monitor website logs and user activity for unusual behavior indicative of exploitation attempts. 8. Consider disabling or replacing the WP Booking Calendar plugin with alternatives if immediate patching is not feasible.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, France, India, Brazil, Japan, Netherlands
CVE-2025-4669: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wpdevelop WP Booking Calendar
Description
The WP Booking Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpbc shortcode in all versions up to, and including, 10.11.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-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
The WP Booking Calendar plugin for WordPress, widely used for managing booking functionalities on websites, contains a stored cross-site scripting vulnerability identified as CVE-2025-4669. This vulnerability stems from CWE-79, improper neutralization of input during web page generation, specifically in the handling of the wpbc shortcode. The plugin fails to adequately sanitize and escape user-supplied attributes before rendering them on pages. As a result, authenticated users with contributor-level permissions or higher can inject arbitrary JavaScript code into pages via the shortcode parameters. When other users access these pages, the malicious scripts execute in their browsers, potentially allowing attackers to steal session cookies, perform actions on behalf of users, or deface content. The vulnerability affects all versions up to and including 10.11.1. Exploitation does not require user interaction beyond page access but does require authentication with contributor or higher privileges, limiting exposure to internal or semi-trusted users. The CVSS 3.1 base score is 6.4, indicating a medium severity level, with the vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N reflecting network attack vector, low attack complexity, privileges required, no user interaction, scope change, and limited confidentiality and integrity impact without availability impact. No patches or exploits are currently publicly available, but the vulnerability poses a risk to websites relying on this plugin, especially those with multiple contributors or untrusted users. Mitigation requires updating the plugin once a fix is released or applying strict input validation and output encoding on shortcode attributes.
Potential Impact
This vulnerability can lead to unauthorized script execution in the context of affected websites, compromising user confidentiality and integrity. Attackers can hijack user sessions, steal sensitive information, or perform unauthorized actions on behalf of users, potentially leading to account compromise or data leakage. Since exploitation requires contributor-level access, the threat is primarily from insiders or compromised accounts with elevated privileges. The vulnerability does not affect system availability but can damage organizational reputation and user trust if exploited. Websites with multiple contributors or public-facing content management are at higher risk. The scope change in the CVSS vector indicates that the vulnerability can affect resources beyond the vulnerable component, increasing potential impact. Although no known exploits exist currently, the medium severity score and ease of exploitation with low complexity suggest organizations should act promptly to mitigate risk.
Mitigation Recommendations
1. Monitor for and apply official patches or updates from the wpdevelop vendor as soon as they become available to address this vulnerability. 2. Until a patch is released, restrict contributor-level access to trusted users only and review user roles to minimize unnecessary privileges. 3. Implement strict input validation and output encoding on all shortcode attributes, especially those accepting user input, to prevent script injection. 4. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious shortcode payloads or script injection attempts. 5. Conduct regular security audits and code reviews of WordPress plugins and themes to identify similar vulnerabilities proactively. 6. Educate content contributors about the risks of injecting untrusted content and enforce content submission policies. 7. Monitor website logs and user activity for unusual behavior indicative of exploitation attempts. 8. Consider disabling or replacing the WP Booking Calendar plugin with alternatives if immediate patching is not feasible.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-05-13T20:54:09.020Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682cd0f81484d88663aeb6ff
Added to database: 5/20/2025, 6:59:04 PM
Last enriched: 2/27/2026, 2:46:44 PM
Last updated: 3/25/2026, 1:33:59 AM
Views: 73
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.