Categories
CVE-2026-92245 high CVSS 7.5

Vulnerability in Simply Schedule Appointments (WordPress plugin) (CVE-2026-92245)

Summary

Vulnerability in Simply Schedule Appointments (WordPress plugin) (CVE-2026-92245). Confidential information can be exposed externally. Exploitable via DELETE /wp-json/ssa/v1/appointments/{id}.

Original description

The description as published by the source.

The Simply Schedule Appointments plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.12.32 via the 'recursive' parameter. This makes it possible for unauthenticated attackers to extract customer PII — including names, email addresses, phone numbers, and custom form field data — stored in appointment records, as well as per-appointment public_token values. The leaked per-appointment public_token values also enable unauthenticated attackers to delete arbitrary appointments via the DELETE /wp-json/ssa/v1/appointments/{id} endpoint, which accepts the token as sole authorization.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-92245 has been found in Simply Schedule Appointments (WordPress plugin).
Attackers can target a specific entry point like DELETE /wp-json/ssa/v1/appointments/{id} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Simply Schedule Appointments (WordPress plugin) CVE-2026-92245" on the vendor's site.

CVE-2026-92245 (Simply Schedule Appointments (WordPress plugin)) — CWE-862 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DELETE /wp-json/ssa/v1/appointments/{id}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in Simply Schedule Appointments (WordPress plugin). Attackers reach the vulnerable code path via DELETE /wp-json/ssa/v1/appointments/{id} without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Simply Schedule Appointments (WordPress plugin). Attack surface: DELETE /wp-json/ssa/v1/appointments/{id}.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /wp-json/ssa/v1/appointments/{id} requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Simply Schedule Appointments (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect
    grep 'DELETE /wp-json/ssa/v1/appointments/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /wp-json/ssa/v1/appointments/{id} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify
    Replay attack against DELETE /wp-json/ssa/v1/appointments/{id} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details