← Back
CVE-2026-52841
low
CVSS 3.1
Vulnerability in alextselegidis/easyappointments (CVE-2026-52841)
Summary
vulnerability in alextselegidis/easyappointments (CVE-2026-52841). Risk of unauthorized operations or information disclosure. Exploitable via ``provider_id``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-52841** has been found in alextselegidis/easyappointments.
Attackers can target a specific entry point like ``provider_id`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "alextselegidis/easyappointments CVE-2026-52841" on the vendor's site.
CVE-2026-52841 (alextselegidis/easyappointments) — CWE-639 / CVSS v3 3.1
Attack vector: remote (network-reachable)
Attack surface: `provider_id` / `oauth_callback` / `select_google_calendar` / `disable_provider_sync`
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-639) exists in alextselegidis/easyappointments. Attackers reach the vulnerable code path via ``provider_id`` without authentication.
📍 Affected scope
alextselegidis/easyappointments — . Attack surface: `provider_id` / `oauth_callback` / `select_google_calendar` / `disable_provider_sync`.
🔥 Severity
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure
🔧 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 request patterns matching this CVE's known IOCs. Run `grep -r 'alextselegidis/easyappointments' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
alextselegidis/easyappointments
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- web https://github.com/alextselegidis/easyappointments/commit/4b2d245d2cd2058dc76e05f6eb65b26699268471
- web https://github.com/alextselegidis/easyappointments/security/advisories/GHSA-8hm4-r66f-29wr
- web https://nvd.nist.gov/vuln/detail/CVE-2026-52841
- web https://github.com/alextselegidis/easyappointments/releases/tag/1.6.0
- web https://github.com/advisories/GHSA-8hm4-r66f-29wr