CVE-2026-57660
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 · uneditedUnauthenticated Broken Access Control in Booking and Rental Manager <= 2.7.1 versions.
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 confidenceUnauthenticated Broken Access Control vulnerability in Booking and Rental Manager plugin for WordPress allows unauthenticated attackers to access functionality or data that should require authentication. The vulnerability affects versions 2.7.1 and below.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Booking and Rental Manager plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Booking and Rental Manager' in the list of active plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status, indicating the plugin files are present on the server.
-
Check installed plugin versionIn the Plugins list, click on the plugin name to view details, or inspect the main plugin file (usually /wp-content/plugins/booking-and-rental-manager/booking-and-rental-manager.php) to find the 'Version' header in the plugin comment block.Affected if The version number displayed is 2.7.1 or lower, placing it within the vulnerable version range.
-
Identify accessible admin endpointsExamine the plugin directory for PHP files that register admin menus or AJAX actions. Look for add_menu_page, add_submenu_page, or wp_ajax_ hooks. Check if these actions lack capability checks (like current_user_can) or nonce verification.Affected if The plugin registers admin functionality (menu pages, AJAX endpoints, or REST routes) that can be accessed without authentication or proper authorization checks.
-
Test unauthenticated access to plugin functionsUsing a tool like curl or Burp Suite, send requests to common plugin endpoints (such as /wp-admin/admin-ajax.php?action=brm_... or direct plugin PHP files) without providing authentication cookies or tokens.Affected if Requests to plugin functionality return successful responses without requiring login, indicating the broken access control is present.
If Booking and Rental Manager version 2.7.1 or below is installed and its admin or AJAX endpoints are accessible without authentication, the environment is affected by this CVE.
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.
From vendor dataUpdate Booking and Rental Manager to the latest version once a patch is released. If no patch is available, consider disabling the plugin until a secure version can be implemented, and restrict plugin admin pages at the web server level as a temporary measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-57660 — 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-2026-57660 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