Missing AuthorizationWeakness · CWE-862

CVE-2026-6937

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-28

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

NVD · unedited

The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.6.11.8 due to the plugin not properly verifying that a user is authorized to perform an action via the bulk appointments REST API endpoint. This makes it possible for unauthenticated attackers to modify arbitrary appointment records including customer PII, payment status, and meeting URL fields, and to expose full customer PII from existing appointment records via the bulk endpoint response. The public nonce is a static, user-independent value present in the HTML source of any page hosting the [ssa_booking] shortcode, meaning any visitor who has viewed such a page can obtain it and target any appointment in the system without authentication.

Technical summary

dbcve analysis · high confidence

The Simply Schedule Appointments plugin fails to enforce authorization checks on its bulk appointments REST API endpoint. The endpoint uses a static, user-independent nonce exposed in the HTML of any page with the [ssa_booking] shortcode, allowing unauthenticated attackers to view and modify arbitrary appointment records including customer PII, payment status, and meeting URLs.

MitigationUpdate the plugin to version 1.6.11.9 or later which contains proper authorization checks; alternatively, temporarily disable the plugin or restrict REST API access at the server level until patching is possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify plugin installation

In WordPress admin, go to Plugins > Installed Plugins and locate 'Simply Schedule Appointments'. Note the version number displayed. Alternatively, check the plugin files in wp-content/plugins/simply-schedule-appointments/

Affected if Plugin is installed and version is below 1.6.11.9
Check for shortcode exposure

Search your WordPress posts, pages, and widgets for the [ssa_booking] shortcode. View the HTML source of any page containing this shortcode and look for a nonce value in a hidden field or script - this nonce is static and user-independent.

Affected if The [ssa_booking] shortcode is present on any public page, exposing the static nonce in HTML
Verify REST API accessibility

Send a GET request to the bulk appointments endpoint (typically /wp-json/ssa/v1/appointments/bulk or similar path under wp-json/ssa/). No authentication should be required to confirm the endpoint responds.

Affected if The REST API endpoint responds without requiring authentication or valid user session
Confirm appointment data exposure

Use the exposed nonce from step 2 to craft a request to the bulk appointments endpoint and examine if appointment records including customer PII, payment status, and meeting URLs are returned without authorization.

Affected if Arbitrary appointment records can be viewed or modified without proper authorization

You are affected if the Simply Schedule Appointments plugin is installed with a version below 1.6.11.9 and the [ssa_booking] shortcode is in use, exposing a static nonce that allows unauthorized access to appointment data via the REST API.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the plugin to version 1.6.11.9 or later which contains proper authorization checks; alternatively, temporarily disable the plugin or restrict REST API access at the server level until patching is possible.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6937 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-6937?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.6%

Remediation

Need this fixed?

Have this fixed 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-6937 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References