CVE-2026-9721: 
WordPress Analyse et atténuation des vulnérabilités

CVE-2026-9721 is a Cross-Site Request Forgery (CSRF) vulnerability in the Book a Room Event Calendar plugin for WordPress, affecting all versions up to and including 1.9. The flaw allows unauthenticated attackers to modify critical plugin configuration settings — including external database credentials and encryption keys — by tricking a logged-in administrator into clicking a malicious link. It was published on June 24, 2026, with a CVSS v3.1 base score of 4.3 (Medium) (GitHub Advisory, Wordfence).

The vulnerability (CWE-352) stems from the complete absence of nonce validation in the plugin's settings_form() and update_settings() functions. The options page handler dispatches on the action POST parameter and calls update_settings(), which persists plugin configuration via WordPress's update_option() without ever calling wp_nonce_field(), check_admin_referer(), or wp_verify_nonce(). This means any forged POST request submitted in the context of an authenticated administrator session will be accepted and processed without verification. The vulnerable code paths are visible in the plugin source at bookaroom-events-settings.php lines 15, 103, and 161 (GitHub Advisory, WordPress Trac).

Successful exploitation allows an unauthenticated attacker to overwrite the plugin's stored configuration, including the external database host, username, password, database name, table prefix, encryption key, and registration page URL. By redirecting the plugin to an attacker-controlled database, the attacker could intercept or manipulate booking and event data, harvest credentials, or disrupt site functionality. While confidentiality and availability impacts are rated as none in the CVSS score, the integrity impact — particularly the ability to alter database connection settings and encryption keys — poses a meaningful risk to data handled by the plugin (GitHub Advisory, Wordfence).

1. Reconnaissance: Identify WordPress sites running the Book a Room Event Calendar plugin version 1.9 or earlier, using tools like WPScan or by checking publicly accessible plugin metadata.
2. Craft forged request: Construct a malicious HTML page or URL that submits a POST request to the target site's WordPress admin settings endpoint (e.g., wp-admin/admin.php?page=bookaroom-settings) with the action parameter set to trigger update_settings() and attacker-controlled values for database host, username, password, prefix, database name, encryption key, and registration page URL.
3. Deliver payload: Send the malicious link or embed the auto-submitting form in a phishing email, forum post, or other medium targeting the site administrator.
4. Administrator triggers request: When the administrator clicks the link or visits the page while logged into WordPress, their browser automatically submits the forged POST request with their authenticated session cookies.
5. Configuration overwritten: The plugin's update_settings() function processes the request without nonce verification and persists the attacker-supplied values via update_option(), redirecting the plugin's database connection to an attacker-controlled host (GitHub Advisory, WordPress Trac).

• Logs: WordPress admin access logs showing unexpected POST requests to wp-admin/admin.php?page=bookaroom-settings or similar plugin settings pages, particularly from unusual referrers or at unexpected times.
• Database: Changes to WordPress wp_options table entries associated with the Book a Room Event Calendar plugin (e.g., database host, username, password, encryption key options) that were not made by a known administrator action.
• Network: Outbound database connection attempts from the WordPress server to unfamiliar or external IP addresses, potentially indicating the plugin was redirected to an attacker-controlled database host.
• File System: No direct file system indicators expected, but review plugin configuration values stored in the database for unauthorized modifications (GitHub Advisory).

Update the Book a Room Event Calendar plugin to a version newer than 1.9 that includes proper nonce validation using wp_nonce_field() in the settings form and check_admin_referer() or wp_verify_nonce() in the handler. A patch has been confirmed as available (GitHub Advisory). As interim mitigations, restrict WordPress admin access to trusted networks, implement Content Security Policy (CSP) headers, and educate administrators about the risks of clicking untrusted links while authenticated to WordPress (Wordfence).