dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-2262

HIGH · 7.5 CVSS v3.1 Published 2026-04-18
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 Easy Appointments plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.12.21 via the `/wp-json/wp/v2/eablocks/ea_appointments/` REST API endpoint. This is due to the endpoint being registered with `'permission_callback' => '__return_true'`, which allows access without any authentication or authorization checks. This makes it possible for unauthenticated attackers to extract sensitive customer appointment data including full names, email addresses, phone numbers, IP addresses, appointment descriptions, and pricing information.

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 Easy Appointments WordPress plugin versions up to 3.12.21 registers a REST API endpoint at `/wp-json/wp/v2/eablocks/ea_appointments/` with a permissive `'permission_callback' => '__return_true'` that allows any unauthenticated user to access the endpoint and retrieve sensitive customer appointment data including names, emails, phone numbers, IPs, appointment details, and pricing.

MitigationReplace the overly permissive permission_callback with proper WordPress authentication/authorization checks (e.g., using `is_user_logged_in()` or capability checks) to restrict endpoint access to authenticated users only.

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. Verify Easy Appointments plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Appointments' or check the plugin files in /wp-content/plugins/easy-appointments/ for version information
    Affected if The plugin is installed and version is 3.12.21 or lower
  2. Confirm the vulnerable REST API endpoint exists
    Send a GET request to /wp-json/wp/v2/eablocks/ea_appointments/ using curl or a browser
    Affected if The endpoint returns an HTTP 200 response (the endpoint exists and is reachable)
  3. Test unauthenticated access to the endpoint
    Make an unauthenticated HTTP request to the endpoint and inspect the response - no login or API keys should be required
    Affected if The endpoint returns appointment data without requiring authentication (any HTTP 2xx response containing appointment records)
  4. Inspect the exposed data fields
    Examine the JSON response from the endpoint to confirm it contains sensitive fields such as customer names, emails, phone numbers, IP addresses, appointment details, and pricing
    Affected if The response includes personal identifiable information (names, emails, phones) or financial data (pricing) without authentication

If the Easy Appointments plugin version 3.12.21 or lower is installed and the /wp-json/wp/v2/eablocks/ea_appointments/ endpoint is accessible without authentication and returns customer data, the environment is affected by CVE-2026-2262.

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

Replace the overly permissive permission_callback with proper WordPress authentication/authorization checks (e.g., using `is_user_logged_in()` or capability checks) to restrict endpoint access to authenticated users only.

Recommended fix Moderate confidence

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

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find the Easy Appointments plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the official WordPress plugin repository (plugins.trac.wordpress.org) and upload it manually
  6. 6. After updating, verify the REST API endpoint `/wp-json/wp/v2/eablocks/ea_appointments/` is no longer publicly accessible or has proper authentication

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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