dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2026-7493

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-27
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 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 Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to denial of service in all versions up to, and including, 1.6.11.5. This is due to a publicly accessible REST API endpoint (/wp-json/ssa/v1/async) that calls PHP's sleep() function on a user-supplied delay parameter without any rate limiting. This makes it possible for unauthenticated attackers to exhaust PHP worker processes, denying access to the site to legitimate users.

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 Simply Schedule Appointments WordPress plugin contains a publicly accessible REST API endpoint (/wp-json/ssa/v1/async) that accepts a user-supplied delay parameter and passes it directly to PHP's sleep() function without any rate limiting or input validation. This allows unauthenticated attackers to repeatedly invoke the endpoint with large delay values, causing PHP worker processes to block and exhaust server resources, resulting in denial of service for legitimate users.

MitigationUpdate the plugin to version 1.6.12 or later which addresses this vulnerability, or implement web application firewall (WAF) rules to rate-limit or block requests to the vulnerable endpoint until the update can be applied.

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
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 the plugin is installed
    Check the WordPress plugins directory for 'simply-schedule-appointments' folder, or query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The Simply Schedule Appointments plugin appears in the active plugins list
  2. Determine installed plugin version
    Read the plugin header from simply-schedule-appointments/ssa.php or simply-schedule-appointments/index.php to find the Version: field, or check in WordPress admin under Plugins > Installed Plugins
    Affected if The version listed is below 1.6.11.6 (or the version cannot be determined and the plugin is present)
  3. Confirm the vulnerable endpoint is accessible
    Send a GET or POST request to /wp-json/ssa/v1/async?delay=5 (or with delay as a POST parameter). A response indicates the endpoint exists.
    Affected if The endpoint returns any valid JSON response (indicating the REST API is registered and reachable)
  4. Test if delay parameter is processed
    Send a request to /wp-json/ssa/v1/async with a delay parameter (e.g., delay=60). Measure the response time - it should take approximately the specified seconds.
    Affected if The response is delayed by approximately the number of seconds specified in the delay parameter

A user is affected if the Simply Schedule Appointments plugin is installed with a version below 1.6.11.6 AND the /wp-json/ssa/v1/async endpoint is accessible and honors the delay parameter, allowing arbitrary sleep injection.

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 the plugin to version 1.6.12 or later which addresses this vulnerability, or implement web application firewall (WAF) rules to rate-limit or block requests to the vulnerable endpoint until the update can be applied.

Recommended fix Moderate confidence

Latest version after 1.6.11.5 (check WordPress plugin repository for current stable release)

  1. 1. Update the Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin to the latest available version from the WordPress plugin repository.
  2. 2. If automatic updates are not enabled, manually update through WordPress admin dashboard > Plugins > Simply Schedule Appointments > Update Now.
  3. 3. Verify the update was successful by confirming the plugin version in the installed plugins list.
  4. 4. Test the site's REST API functionality to ensure the endpoint is now properly secured or rate-limited.
Caveat Review plugin changelog for any breaking changes between your current version and the new version, particularly regarding booking functionality

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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