# CVE-2026-23622: CSRF Protection Bypass: Sensitive endpoints accept GET requests, enabling admin account takeover

> Attackers can bypass CSRF protection via GET requests to create or modify admin accounts, leading to full administrative takeover of the Easy!Appointments system.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2026
- **Updated:** 15 Jan 2026
- **Also known as:** GHSA-54v4-4685-vwrj

## What is CVE-2026-23622?

CVE-2026-23622 is a high-severity vulnerability in alextselegidis easyappointments, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Easy!Appointments is a self hosted appointment scheduler. In 1.5.2 and earlier, application/core/EA_Security.php::csrf_verify() only enforces CSRF for POST requests and returns early for non-POST methods. Several application endpoints perform state-changing operations while accepting parameters from GET (or $_REQUEST), so an attacker can perform CSRF by forcing a victim's browser to issue a crafted GET request. Impact: creation of admin accounts, modification of admin email/password, and full admin account takeover.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-23622?

2 open source packages ship an affected version, including alextselegidis/easyappointments. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `alextselegidis/easyappointments` | Packagist | All versions to 1.5.2 | None |
| `alextselegidis/easyappointments` | Packagist | All versions to 1.5.2 | None |

Products: Easyappointments Easy\!appointments.

## How do I fix CVE-2026-23622?

No fix has been published for CVE-2026-23622 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-23622 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23622 exists.

## Other vulnerabilities in alextselegidis easyappointments

- [CVE-2025-50383](https://insights.sbomify.com/CVE-2025-50383/): Easy!Appointments SQL injection vulnerability (high 8.1)
- [CVE-2025-29448](https://insights.sbomify.com/CVE-2025-29448/): Easy!Appointments Denial of Service (DoS) (high 7.5)
- [CVE-2018-13063](https://insights.sbomify.com/CVE-2018-13063/): Missing authorization in n/a (high 7.5)
- [CVE-2018-13060](https://insights.sbomify.com/CVE-2018-13060/): Security feature bypass in n/a (medium 6.5)
- [CVE-2024-0698](https://insights.sbomify.com/CVE-2024-0698/): Easy!Appointments <= 1.3.1 - Authenticated (Contributor+) Stored Cross-Site Scripting (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23622 and fix it if it is affected.

What it is: CVE-2026-23622 is a high-severity vulnerability in alextselegidis easyappointments, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23622 exists.

Affected packages and fixed versions:
- alextselegidis/easyappointments (Packagist): affected all versions up to 1.5.2; no fix listed
- alextselegidis/easyappointments (Packagist): affected all versions up to 1.5.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23622/ (Markdown: https://insights.sbomify.com/CVE-2026-23622/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23622
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23622
- OSV: https://osv.dev/vulnerability/CVE-2026-23622

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23622/
Summaries are generated and may contain mistakes; the official description above is the record.