dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-39390

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 magepeopleteam Booking and Rental Manager booking-and-rental-manager-for-woocommerce allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Booking and Rental Manager: from n/a through <= 2.3.6.

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 Booking and Rental Manager plugin for WooCommerce allows unauthenticated or unauthorized users to access functionality that should be restricted by access control lists (ACLs). This is a classic IDOR or privilege escalation issue where proper capability checks are not enforced on certain WordPress AJAX endpoints or admin pages.

MitigationUpdate to the latest version of Booking and Rental Manager when available, or add proper WordPress capability checks (e.g., current_user_can()) and nonce verification to all AJAX handlers and admin functions in the plugin.

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
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. Verify Booking and Rental Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and confirm 'Booking and Rental Manager' or 'Booking and Rental Manager for WooCommerce' appears in the list. Note the installed version displayed next to the plugin name.
    Affected if The plugin is installed and active in the WordPress environment
  2. Identify installed plugin version
    Check the plugin version in the plugin header (typically in the main plugin file, e.g., booking-and-rental-manager.php) by opening the file via file manager or FTP, or use a security scanner to enumerate plugin versions.
    Affected if The installed version lacks the security fix for missing authorization checks
  3. Inspect AJAX endpoint capability checks
    Locate all AJAX handlers in the plugin (files containing add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...')). Open each handler and verify that current_user_can() or a proper capability check is present at the start of the function before any data processing or database operations.
    Affected if AJAX handlers lack current_user_can() checks or allow wp_ajax_nopriv_ actions without proper authorization validation
  4. Check for nonce verification in admin functions
    Review all functions hooked to admin_menu, admin_init, or other admin actions. For each, search for wp_verify_nonce() or check_admin_referer() calls. Verify nonces are validated before executing privileged operations.
    Affected if Admin functions perform sensitive operations without nonce verification, allowing CSRF attacks
  5. Test unauthenticated access to restricted endpoints
    Use a tool like Burp Suite or curl to send requests to known AJAX endpoints (e.g., wp-admin/admin-ajax.php?action=brm_...) without authentication credentials. Check if the endpoint returns successful responses instead of 401/403 errors.
    Affected if Requests without valid authentication or authorization tokens succeed in accessing restricted plugin functionality

The environment is affected if the Booking and Rental Manager plugin is installed and its AJAX endpoints or admin functions lack proper capability checks (current_user_can()) and nonce verification, allowing unauthorized access.

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

Update to the latest version of Booking and Rental Manager when available, or add proper WordPress capability checks (e.g., current_user_can()) and nonce verification to all AJAX handlers and admin functions in the plugin.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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