CVE-2025-58991
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Cristiano Zanca WooCommerce Booking Bundle Hours allows Stored XSS. This issue affects WooCommerce Booking Bundle Hours: from n/a through 0.7.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Booking Bundle Hours WordPress plugin (versions through 0.7.4) allows attackers to inject malicious JavaScript through stored XSS by tricking authenticated administrators into submitting crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WooCommerce Booking Bundle Hours plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'WooCommerce Booking Bundle Hours' in the list, or inspect the wp-content/plugins/ directory for a folder containing 'booking-bundle-hours' or similar naming.Affected if The plugin is not found in the WordPress installation.
-
Identify the installed plugin versionIn WordPress admin Plugins list, click on the plugin to view details and read the version number from the plugin header. Alternatively, open the main plugin PHP file (usually the primary .php file in the plugin folder) and look for the 'Version:' field in the plugin comment header.Affected if Version is 0.7.4 or lower, or the version field cannot be determined (plugin may be outdated or from a modified source).
-
Confirm the plugin is activeIn WordPress admin Plugins > Installed Plugins, check if WooCommerce Booking Bundle Hours shows 'Active' status under the plugin name.Affected if Plugin is active and running on the site.
-
Check for recent admin configuration changesReview WordPress activity logs or audit logs for any suspicious admin action events, particularly around plugin settings pages. Look for unexpected POST/GET requests to admin-ajax.php or plugin settings pages that may indicate CSRF exploitation.Affected if Unusual admin actions or settings changes were made without legitimate admin authorization.
Your environment is affected if the WooCommerce Booking Bundle Hours plugin is installed, active, and running version 0.7.4 or lower, exposing admin users to CSRF-triggered stored XSS attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the WooCommerce Booking Bundle Hours plugin to the latest version; if no patch is available, disable the plugin and implement anti-CSRF tokens in any custom implementations.
- Consultation3.0 h
- Implementation5.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58991 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58991 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data