Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-4669 Overview
CVE-2025-4669 is a stored Cross-Site Scripting (XSS) vulnerability in the WP Booking Calendar plugin for WordPress. The flaw affects all versions up to and including 10.11.1. It originates in the plugin's wpbc shortcode, where user-supplied attributes are not properly sanitized or escaped before being rendered. Authenticated users with contributor-level privileges or higher can inject arbitrary JavaScript into pages. The injected scripts execute in the browser of any visitor accessing the affected page. The issue is tracked under CWE-79 and was addressed in WordPress Changeset #3293836.
Critical Impact
Contributor-level attackers can inject persistent JavaScript via the wpbc shortcode, enabling session theft, administrative action hijacking, and malicious redirects for every visitor who loads the page.
Affected Products
- WP Booking Calendar plugin for WordPress, all versions up to and including 10.11.1
- WordPress sites allowing contributor-level or higher user registration
- Websites embedding the wpbc shortcode in posts or pages
Discovery Timeline
- 2025-05-17 - CVE-2025-4669 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-4669
Vulnerability Analysis
The vulnerability is a stored XSS flaw rooted in insufficient input sanitization and output escaping within the WP Booking Calendar plugin. When WordPress renders the wpbc shortcode, the plugin processes user-controlled attributes and emits them into the page markup without applying appropriate escaping functions such as esc_attr() or esc_html(). An authenticated attacker holding contributor privileges or higher can save a post containing the shortcode with a crafted attribute payload. The malicious payload persists in the database and executes whenever any user loads the rendered page.
Because execution occurs in the context of the victim's browser session, an attacker who targets an authenticated administrator can trigger script-driven actions under administrator authority. The scope change (S:C in the vector) reflects that script executes beyond the vulnerable component. The EPSS probability is 0.36%, placing the vulnerability in the 27.9th percentile.
Root Cause
The plugin's shortcode handler returns attribute values directly into HTML output without sanitizing them against script content. Relevant handling appears in the plugin source at lines 248, 445, and 789 of wpdev-booking-class.php. WordPress's shortcode API does not auto-escape attributes, so individual plugins must enforce escaping themselves.
Attack Vector
The attack requires network access to the WordPress site and authentication at the contributor role or higher. The attacker creates or edits a post, inserts the wpbc shortcode with a crafted attribute carrying a JavaScript payload, and submits the content. When a visitor or administrator loads the page, the browser parses the injected markup and executes the attacker's script in the site's origin.
No verified public exploit code is available. Technical details are described in the Wordfence Vulnerability Analysis.
Detection Methods for CVE-2025-4669
Indicators of Compromise
- Posts or pages containing the wpbc shortcode with attribute values that include HTML tags, javascript: URIs, or event handler strings such as onerror= or onload=
- Newly created or recently promoted contributor accounts followed by edits to pages containing the wpbc shortcode
- Unexpected outbound HTTP requests from visitor browsers to attacker-controlled domains originating from pages rendering WP Booking Calendar content
Detection Strategies
- Query the WordPress wp_posts table for post content matching patterns like [wpbc combined with <script, onerror, onload, or javascript:
- Review web server access logs for POST requests to /wp-admin/post.php or /wp-admin/post-new.php by contributor-level accounts that include shortcode payloads
- Monitor browser-side error telemetry or Content Security Policy (CSP) violation reports for script execution on pages rendering the wpbc shortcode
Monitoring Recommendations
- Enable auditing on contributor and author role assignments to catch suspicious role escalations or new account creation
- Track plugin version inventory across WordPress deployments and alert on sites still running WP Booking Calendar 10.11.1 or earlier
- Deploy a web application firewall (WAF) rule to inspect post content submitted by non-administrator accounts for shortcode-embedded script content
How to Mitigate CVE-2025-4669
Immediate Actions Required
- Update the WP Booking Calendar plugin to the version released after changeset 3293836, which addresses the sanitization gap
- Audit all posts and pages that include the wpbc shortcode and remove any attribute values containing script content or suspicious markup
- Review contributor, author, and editor accounts; disable or remove accounts that are inactive, unverified, or recently created
Patch Information
The plugin maintainers addressed the vulnerability in the commit documented at WordPress Changeset #3293836. The fix adds proper sanitization and output escaping to the wpbc shortcode attribute handling in wpdev-booking-class.php. Site administrators should install the patched version through the WordPress plugin updater. Additional vendor information is available on the WordPress Booking Plugin Developers page.
Workarounds
- Restrict post creation and editing privileges by removing the contributor role from untrusted users until the patch is applied
- Deactivate the WP Booking Calendar plugin on sites that do not require booking functionality until it can be updated
- Enforce a strict Content Security Policy that blocks inline scripts and restricts script sources to trusted origins to limit payload execution
# Update WP Booking Calendar via WP-CLI
wp plugin update booking
# Verify the installed version is above 10.11.1
wp plugin get booking --field=version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

