dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-6814

HIGH · 7.5 CVSS v3.1 Published 2025-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Booking X plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the export_now() function in versions 1.0 to 1.1.2. This makes it possible for unauthenticated attackers to download all plugin data, including user accounts, user meta, and PayPal credentials, by issuing a crafted POST request.

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 Booking X WordPress plugin has a broken access control vulnerability where the export_now() function lacks a capability check, allowing unauthenticated attackers to export all plugin data including user accounts, user meta, and PayPal credentials via a crafted POST request.

MitigationUpdate to the latest patched version of Booking X. If no patch is available, disable the plugin immediately and block the vulnerable endpoint at the web application firewall level while investigating potential data exfiltration.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Confirm Booking X plugin installation and version
    Locate the Booking X plugin in your WordPress installation (typically in /wp-content/plugins/booking-x/) and check the main plugin file for the version number, or use 'wp plugin list' via WP-CLI
    Affected if The plugin is installed and the version is lower than the patched version
  2. Identify the vulnerable export_now() function
    Examine the plugin source code, specifically looking for the export_now() function in the plugin files (often in includes/admin/ or similar directories)
    Affected if The export_now() function exists and lacks a capability check (look for missing 'current_user_can()' or 'wp_verify_nonce()' before the export logic)
  3. Verify the export endpoint accepts unauthenticated requests
    Check the plugin's AJAX handlers or route registrations to see if the export functionality is hooked to an action accessible to unauthenticated users (common hooks: wp_ajax_nopriv_, admin_post_, or direct function calls)
    Affected if The export functionality is reachable without authentication (no capability verification on the handler)
  4. Review server logs for suspicious export POST requests
    Search your web server access logs (Apache/Nginx) for POST requests to URLs containing 'export', 'download', or 'bkx_export' patterns originating from unfamiliar or unauthorized IP addresses
    Affected if Unexpected export requests appear in logs, especially from unauthenticated sources or unusual IP addresses

Your environment is affected if Booking X plugin is installed with a version lacking the capability check patch, and the export endpoint is reachable 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of Booking X. If no patch is available, disable the plugin immediately and block the vulnerable endpoint at the web application firewall level while investigating potential data exfiltration.

Recommended fix Moderate confidence

Latest version of Booking X plugin (version 1.1.3 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Booking X plugin
  4. Check the current version number
  5. If the installed version is 1.1.2 or below, update the plugin to the latest available version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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