dbcve.org
WpbookitWordPress extension · Iqonic

CVE-2025-0357

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-25
Fix available
A fix is available. Upgrade to 1.6.10 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The WPBookit plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'WPB_Profile_controller::handle_image_upload' function in versions up to, and including, 1.6.9. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 · high confidence

The WPBookit WordPress plugin has an arbitrary file upload vulnerability in versions up to 1.6.9. The WPB_Profile_controller::handle_image_upload function fails to properly validate file types, allowing unauthenticated attackers to upload arbitrary files including malicious executables, potentially achieving remote code execution.

MitigationUpdate WPBookit plugin to version 1.6.10 or later. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious file uploads.

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.6.10

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
High
Integrity
High
Availability
High

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

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 WPBookit plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wpbookit' or 'iqonic-wpbookit', or view the installed plugins list via WordPress admin under Plugins > Installed Plugins
    Affected if The WPBookit plugin folder exists in the plugins directory
  2. Identify the installed WPBookit version
    If the plugin folder exists, open the main plugin file (typically wpbookit.php or index.php inside the plugin folder) and locate the version declaration in the plugin header comment, or check the version shown in WordPress admin under Plugins > Installed Plugins > WPBookit
    Affected if The version number found is less than 1.6.10 (for example, 1.6.9, 1.6.8, etc.)
  3. Verify the vulnerable upload function exists
    Inspect the plugin files for the presence of 'WPB_Profile_controller' class and 'handle_image_upload' function - these are typically located in a controller or class file within the plugin structure
    Affected if The file containing WPB_Profile_controller::handle_image_upload exists in the plugin directory
  4. Confirm the upload endpoint is accessible
    Check if the WordPress REST API or AJAX endpoint for profile image uploads is publicly accessible (no authentication required) - this is typically at wp-json/wpbookit/v1/upload or similar, and can be tested by making a POST request to that endpoint without credentials
    Affected if The upload endpoint responds without requiring authentication

A user is affected if the WPBookit plugin version is below 1.6.10 AND the vulnerable upload function exists and is accessible without authentication.

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.

dbcve · scoped
Upgrade available Upgrade to 1.6.10 or later
Fixed in 1.6.10
Interim mitigation

Update WPBookit plugin to version 1.6.10 or later. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block suspicious file uploads.

Recommended fix High confidence

1.6.10

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WPBookit in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.6.10 of the plugin
  5. Verify the plugin version shows 1.6.10 after updating
  6. Test that the profile image upload functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpbookit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0357 — 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-0357 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