WpbookitWordPress extension · Iqonic
CVE-2025-6058
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 · uneditedThe WPBookit plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the image_upload_handle() function hooked via the 'add_booking_type' route in all versions up to, and including, 1.0.4. 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 confidenceThe WPBookit WordPress plugin fails to validate file types in its image_upload_handle() function, which is hooked to the 'add_booking_type' REST API route. This allows unauthenticated attackers to upload any file type, including executable PHP scripts, directly to the server's web directory.
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
< 1.0.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WPBookit plugin versionCheck the installed version via WordPress admin (Plugins > WPBookit) or inspect the main plugin file header in wp-content/plugins/iqonic-wpbookit/ or wp-content/plugins/wpbookit/ for the 'Version' fieldAffected if The installed version is 1.0.4 or lower (versions prior to 1.0.5 are affected)
-
Confirm the vulnerable REST API endpoint existsSend a GET request to your site's /wp-json/wpbookit/v1/add_booking_type endpoint using curl or a browser. No authentication should be required to access this route.Affected if The endpoint responds with a valid JSON structure (even if it returns an error), indicating the vulnerable function is registered and accessible to unauthenticated users
-
Inspect upload directories for suspicious filesExamine the wp-content/uploads/ directory (and any custom upload paths configured for WPBookit) for unfamiliar files with extensions such as .php, .phtml, .exe, .js, or .sh that were not intentionally uploaded through legitimate plugin featuresAffected if Unexpected executable or script files exist in upload directories that were not deliberately placed there by administrators
-
Review server access logs for upload attemptsSearch web server access logs (Apache error.log, Nginx access.log) for POST requests to /wp-json/wpbookit/v1/add_booking_type and look for patterns indicating file upload payloadsAffected if Log entries show POST requests to this endpoint containing file upload parameters or unusual filename patterns
-
Check for recently modified PHP files in uploadsUse find command (e.g., find /path/to/wp-content/uploads -name "*.php" -mtime -7) to locate PHP files created or modified within recent days in upload directoriesAffected if PHP files or other executable scripts exist in upload directories with recent modification timestamps indicating potential exploitation
If the WPBookit plugin version is 1.0.4 or lower AND the add_booking_type REST API endpoint is accessible without authentication, the environment is vulnerable to arbitrary file upload 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.
dbcve · scoped1.0.5
Update WPBookit to the latest version when available. Immediately disable the plugin if an update is not available, or add firewall rules/web.config restrictions to block execution of uploaded files in the uploads directory.
1.0.5
- Back up your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find WPBookit in the plugin list
- Click 'Update now' if an update is available, or manually upload version 1.0.5 of the plugin
- Verify the update was successful by checking the plugin version
- Confirm the image_upload_handle() function now properly validates file types
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
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6058 — 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-6058 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