Vulnerability in alextselegidis/easyappointments (CVE-2026-52839)
Summary
Vulnerability in alextselegidis/easyappointments (CVE-2026-52839). Risk of unauthorized operations or information disclosure. Exploitable via POST /index.php/appointments/store. Mitigation: upgrade to 1.6.0 or later.
Original description
The description as published by the source.
Easy!Appointments is a self hosted appointment scheduler. Versions prior to 1.6.0 correctly filter provider-scoped appointments in the appointments/search response, proving that provider isolation is an intended security boundary. However, the direct mutation endpoints appointments/store and appointments/update only check generic appointment privileges and never verify that the submitted id_users_provider belongs to the current session. A normal authenticated provider can inject new appointments into another provider's schedule via store, or reassign existing appointments into a foreign provider's calendar via update. The store path contains an additional write-before-crash bug: the unauthorized row is committed to the database before the controller crashes on a type error, so the attacker receives an error response while the foreign appointment is already persisted. Version 1.6.0 patches the issue.
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-52839 has been found in alextselegidis/easyappointments.
Attackers can target a specific entry point like POST /index.php/appointments/store over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade alextselegidis/easyappointments to 1.6.0 or later.
If unsure, ask your IT team or search "alextselegidis/easyappointments CVE-2026-52839" on the vendor's site.
CVE-2026-52839 (alextselegidis/easyappointments) — CWE-639 / CVSS v3 3.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /index.php/appointments/store / POST /index.php/appointments/update / id_users_provider / store
Patched: 1.6.0 — apply immediately
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.
A vulnerability (CWE-639) exists in alextselegidis/easyappointments. Attackers reach the vulnerable code path via POST /index.php/appointments/store.
Check the vendor advisory for the affected versions of alextselegidis/easyappointments. Attack surface: POST /index.php/appointments/store / POST /index.php/appointments/update / id_users_provider / store.
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.6.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /index.php/appointments/store requests with malformed payloads or SQL meta-characters. Run grep -r 'alextselegidis/easyappointments' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'alextselegidis/easyappointments' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
alextselegidis/easyappointmentsを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /index.php/appointments/store' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /index.php/appointments/storeへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade alextselegidis/easyappointments to 1.6.0ステージング環境で 1.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /index.php/appointments/store on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web security-advisories@github.com
- web github.com
- web github.com