dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-39541

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Roland Murg WP Simple Booking Calendar wp-simple-booking-calendar.This issue affects WP Simple Booking Calendar: from n/a through <= 2.0.13.

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 WP Simple Booking Calendar plugin for WordPress allows attackers to access sensitive functionality without proper authentication or authorization checks. The vulnerability exists in version 2.0.13 and below, likely enabling unauthorized users to perform calendar booking operations that should require authentication.

MitigationUpdate WP Simple Booking Calendar to the latest version which includes proper authorization checks. Until then, restrict access to the plugin's admin pages via server-side access controls and monitor for unauthorized access attempts.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 WP Simple Booking Calendar is installed
    Locate the plugin directory in your WordPress installation (wp-content/plugins/simple-booking-calendar) or check via WordPress admin under Plugins
    Affected if The plugin directory exists in the WordPress installation
  2. Check the installed plugin version
    Open the main plugin file (typically simple-booking-calendar.php) and locate the version declaration in the file header, or view version via WordPress admin Plugins page
    Affected if The version number is 2.0.13 or lower
  3. Verify the plugin is active
    Check the WordPress admin Plugins page to confirm the plugin status shows as 'Active', or query the wp_options table for the active_plugins option
    Affected if The plugin appears as active in WordPress
  4. Identify exposed booking endpoints
    Review the plugin files for AJAX handlers (wp-admin/admin-ajax.php) or public-facing form actions that process booking submissions without capability checks
    Affected if The plugin exposes booking-related functionality accessible without authentication

Your environment is affected if WP Simple Booking Calendar version 2.0.13 or below is installed and active, exposing booking operations that lack proper authorization checks.

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 WP Simple Booking Calendar to the latest version which includes proper authorization checks. Until then, restrict access to the plugin's admin pages via server-side access controls and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

latest version available from WordPress plugin repository or vendor (version higher than 2.0.13)

  1. 1. Check the plugin settings and WordPress admin panel for any unauthorized bookings or modifications.
  2. 2. Review access logs and user activity to identify any unauthorized actions taken through the vulnerability.
  3. 3. Update WP Simple Booking Calendar to the latest available version from the WordPress plugin repository or vendor.
  4. 4. After updating, verify that proper authorization checks are in place by testing functionality with different user roles.
  5. 5. Consider implementing additional access controls at the web server level (e.g., .htaccess rules) to restrict admin area access to authorized users only until the plugin is updated.
Caveat Review plugin changelog for any breaking changes between current and new version

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

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