dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39513

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
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
Unauthenticated Broken Access Control in Easy Appointments <= 3.12.21 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 confidence

Unauthenticated broken access control vulnerability in Easy Appointments plugin for WordPress versions 3.12.21 and below allows unauthenticated attackers to access administrative or privileged functionality they should not have access to.

MitigationUpdate Easy Appointments plugin to the latest version as soon as a patched release is available, or implement additional access controls at the server/web application level until the vendor patch is released.

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 Easy Appointments plugin is installed
    Navigate to WordPress admin dashboard > Plugins page and look for 'Easy Appointments' in the list of installed plugins, or check the /wp-content/plugins/ directory for the easy-appointments folder
    Affected if Easy Appointments plugin is present in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin > Plugins page, click on 'Easy Appointments' to view the plugin details, which displays the version number. Alternatively, check the main plugin file (e.g., easy-appointments.php) for the 'Version' header comment
    Affected if The displayed version is 3.12.21 or lower
  3. Verify plugin is active
    In WordPress admin > Plugins > Installed Plugins, confirm the Easy Appointments plugin shows as 'Active'
    Affected if The plugin is activated and running on the site
  4. Check for unauthorized access exposure
    Inspect HTTP responses and server logs for any requests to admin-ajax.php, admin-post.php, or other WordPress admin endpoints that occur without authentication (without valid user session). Look for successful responses (HTTP 200) to privileged actions that should require login
    Affected if Unauthenticated requests to administrative functions return successful responses indicating broken access control
  5. Review user role capabilities
    Test whether unauthenticated (logged-out) users can access Easy Appointments scheduling or admin features by attempting to access common plugin endpoints directly
    Affected if Unauthenticated users can access pages or perform actions that require administrator or privileged user roles

If Easy Appointments plugin is installed at version 3.12.21 or below and is active, the site is affected by this unauthenticated broken access control vulnerability.

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 Easy Appointments plugin to the latest version as soon as a patched release is available, or implement additional access controls at the server/web application level until the vendor patch is released.

Recommended fix Moderate confidence

Upgrade to Easy Appointments version 3.12.22 or later (the latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Easy Appointments plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 3.12.22 or higher
  6. 6. Test the appointment booking functionality to ensure the plugin still works correctly after the update
Caveat Minor or no breaking changes expected for security updates; always test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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