CVE-2025-58991

7.1 HIGH

📋 TL;DR

A Cross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Booking Bundle Hours WordPress plugin allows attackers to perform unauthorized actions on behalf of authenticated users. When exploited, this CSRF vulnerability can lead to Stored Cross-Site Scripting (XSS), enabling attackers to inject malicious scripts into the website. This affects all WordPress sites using WooCommerce Booking Bundle Hours plugin versions up to 0.7.4.

💻 Affected Systems

Products:
  • WooCommerce Booking Bundle Hours WordPress Plugin
Versions: All versions up to and including 0.7.4
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress with WooCommerce and the Booking Bundle Hours plugin installed. The vulnerability is present in default configurations.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could inject malicious JavaScript that steals administrator credentials, hijacks user sessions, redirects visitors to malicious sites, or defaces the website. This could lead to complete site compromise and data theft.

🟠

Likely Case

Attackers trick administrators into performing unintended actions (like adding malicious scripts) through crafted links or forms, leading to persistent XSS payloads that affect all site visitors.

🟢

If Mitigated

With proper CSRF tokens and input validation, the vulnerability would be prevented, and even if exploited, proper output encoding would neutralize XSS payloads.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires tricking an authenticated user (typically an administrator) to click a malicious link or visit a crafted page. CSRF to XSS chain is well-documented and easily weaponized.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.7.5 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/woo-booking-bundle-hours/vulnerability/wordpress-woocommerce-booking-bundle-hours-plugin-0-7-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'WooCommerce Booking Bundle Hours' and check if update is available. 4. Click 'Update Now' to install version 0.7.5 or later. 5. Verify the plugin is active and functioning correctly.

🔧 Temporary Workarounds

Temporary Plugin Deactivation

linux

Disable the vulnerable plugin until patched to prevent exploitation.

wp plugin deactivate woo-booking-bundle-hours

CSRF Protection via .htaccess

all

Add basic CSRF protection headers at web server level (limited effectiveness).

Header set X-Frame-Options "SAMEORIGIN"
Header set Content-Security-Policy "frame-ancestors 'self'"

🧯 If You Can't Patch

  • Disable the WooCommerce Booking Bundle Hours plugin immediately.
  • Implement web application firewall (WAF) rules to block CSRF attempts and XSS payloads.

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin > Plugins > Installed Plugins for 'WooCommerce Booking Bundle Hours' version. If version is 0.7.4 or lower, you are vulnerable.

Check Version:

wp plugin get woo-booking-bundle-hours --field=version

Verify Fix Applied:

After updating, verify the plugin version shows 0.7.5 or higher in WordPress admin > Plugins > Installed Plugins.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to WordPress admin-ajax.php or admin-post.php endpoints related to booking functionality
  • Multiple failed CSRF token validation attempts in WordPress debug logs

Network Indicators:

  • Unexpected outbound connections from your WordPress site to external domains following admin actions
  • Suspicious referrer headers in requests to booking-related endpoints

SIEM Query:

source="wordpress.log" AND ("admin-ajax.php" OR "admin-post.php") AND ("booking" OR "bundle-hours") AND status=200

🔗 References

📤 Share & Export