dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-7852

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 missing file type validation in the image_upload_handle() function hooked via the 'add_new_customer' route in all versions up to, and including, 1.0.6. The plugin’s image‐upload handler calls move_uploaded_file() on client‐supplied files without restricting allowed extensions or MIME types, nor sanitizing the filename. 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 its image_upload_handle() function accessed via the 'add_new_customer' route. The function calls move_uploaded_file() on client-supplied files without validating file extensions, checking MIME types, or sanitizing filenames, allowing unauthenticated attackers to upload arbitrary files including malicious scripts.

MitigationUntil a patched version is available, disable the plugin or implement web server-level restrictions to block executable file uploads. Apply proper validation including extension whitelisting, MIME type verification, and filename sanitization to the upload handler.

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
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. Confirm WPBookit plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPBookit' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wpbookit' or similar.
    Affected if WPBookit plugin is present in the WordPress installation
  2. Identify WPBookit version
    In WordPress admin, click on the WPBookit plugin to view its details and version number. If not visible there, check the plugin's main PHP file header for a 'Version' comment or the readme.txt file.
    Affected if The installed version matches or precedes the affected version range (if known)
  3. Verify the add_new_customer endpoint exists
    Check the plugin's routes/URLs to confirm the 'add_new_customer' endpoint is registered. This is typically found in the plugin's main PHP file or router configuration. Access the URL /wp-admin/admin-ajax.php?action=add_new_customer or the REST API route if used.
    Affected if The endpoint responds (even with an error) indicating the route is active
  4. Inspect image_upload_handle function for validation
    Locate the image_upload_handle() function in the plugin files (search in plugin PHP files). Examine the function code to see if it calls move_uploaded_file() without extension validation, MIME type checks, or filename sanitization.
    Affected if The function contains move_uploaded_file() without proper validation checks
  5. Test file upload capability (non-exploitative)
    Submit a benign test request to the add_new_customer endpoint with a harmless file (e.g., a text file) and observe if it is accepted and stored. Do not upload executable files. Check the uploads directory for the file.
    Affected if The file upload succeeds without validation errors, indicating the vulnerability is present

A defender is affected if WPBookit is installed with a vulnerable version, the add_new_customer endpoint exists, and the image_upload_handle() function lacks proper file validation before calling move_uploaded_file().

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until a patched version is available, disable the plugin or implement web server-level restrictions to block executable file uploads. Apply proper validation including extension whitelisting, MIME type verification, and filename sanitization to the upload handler.

Have this fixed 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 help mitigating

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-7852 — 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-7852 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