dbcve.org
WpbookitWordPress extension · Iqonic

CVE-2025-32254

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-04
Fix available
A fix is available. Upgrade to after 1.0.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Iqonic Design WPBookit wpbookit allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WPBookit: from n/a through <= 1.0.7.

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 confidence

Missing authorization vulnerability in the WPBookit WordPress plugin allows unauthenticated or unauthorized users to access functionality that should be constrained by access control lists (ACLs). This broken access control issue enables attackers to potentially interact with booking management functions without proper privilege verification.

MitigationImplement proper capability checks and role-based access controls on all sensitive functions within the plugin. Verify user authentication state and authorization before executing any privileged operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WpbookitWordPress extension
Affected:<= 1.0.3

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Iqonic Wpbookit plugin installation
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'wpbookit', 'iqonic-wpbookit', or similar. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to find 'Iqonic Wpbookit' or 'Wpbookit' in the list.
    Affected if The plugin folder or listing exists in the WordPress installation
  2. Verify the installed version
    In the WordPress admin under Plugins > Installed Plugins, find the plugin entry and note the version number displayed. Alternatively, open the main plugin PHP file (usually wp-content/plugins/[plugin-folder]/wpbookit.php or similar) and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is 1.0.3 or any earlier version (1.0.0 through 1.0.3)
  3. Confirm the plugin is active
    In WordPress admin under Plugins > Installed Plugins, check if the plugin has an 'Active' status or 'Activate' link. Alternatively, check the wp_options table for an active_plugins entry containing the plugin folder name.
    Affected if The plugin status is Active and accessible on the site
  4. Identify exposed AJAX or admin endpoints
    Examine the plugin PHP files for action hooks registered with add_action() using 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes, or any publicly accessible functions handling booking operations. Common paths include wp-content/plugins/[plugin-folder]/includes/ or the main plugin file.
    Affected if The plugin registers AJAX handlers accessible to unauthenticated users (wp_ajax_nopriv_) or exposes booking management functions without capability checks

If the Iqonic Wpbookit plugin is installed at version 1.0.3 or lower and is active, the site is affected by this broken access control vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.3
Interim mitigation

Implement proper capability checks and role-based access controls on all sensitive functions within the plugin. Verify user authentication state and authorization before executing any privileged operations.

Fix this in Wpbookit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32254 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32254 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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