Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

GHSA-r6cm-wg48-rh2r alextselegidis/easyappoin…

CRITICALFix: alextselegidis/easyappointments@44af526

GHSA-r6cm-wg48-rh2r is a critical-severity (CVSS 9.1) CWE-359 vulnerability in alextselegidis/easyappointments. 5 public exploit references exist, so weaponization risk is real. A fix is available for alextselegidis/easyappointments — see the affected versions and patch details below.

Exposure of Private Personal Information to an Unauthorized Actor in alextselegidis/easyappointments

Also known asCVE-2022-0482
Published
Mar 10, 2022
Updated
Feb 19, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
5 known
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
43.7%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-r6cm-wg48-rh2r plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐘alextselegidis/easyappointments

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The software is a booking management system that has a public form to place bookings, and a private area for the calendar and management of services, users, settings, etc. There is a backend API that allows data manipulation, including listing the appointments for a specific time range. This happens on this endpoint: /index.php/backend_api/ajax_get_calendar_events Unfortunately, there is no authentication / permissions-check on that endpoint, the only required parameters in a POST request are "startDate", "endDate" and "csrfToken". Because the csrfToken can be obtained by any unauthenticated user just visiting the public form (and is valid for the backend as well), any attacker can query the backend API and obtain all sorts of private information about the appointment, in JSON format.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistalextselegidis/easyappointmentsall versions1.4.3composer require alextselegidis/easyappointments:^1.4.3
Exploits & PoCs
5

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-50871webappsphp

Easy Appointments 1.4.2 - Information Disclosure

by Alexandre ZANNI · Apr 19, 2022

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for alextselegidis/easyappointments, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update alextselegidis/easyappointments to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6cm-wg48-rh2r is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r6cm-wg48-rh2r can be triaged on real exposure rather than presence alone.

Tailored to GHSA-r6cm-wg48-rh2r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect GHSA-r6cm-wg48-rh2r

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-r6cm-wg48-rh2r -u https://target
Template
Easy!Appointments <1.4.3 - Broken Access Control
Severity
critical
Impact
An attacker can exploit this vulnerability to gain unauthorized access to sensitive data or perform unauthorized actions.
Remediation
Upgrade Easy!Appointments to version 1.4.4 or above to fix the Broken Access Control vulnerability.

Template by ProjectDiscovery nuclei-templates (francescocarlucci, opencirt), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

The software is a booking management system that has a public form to place bookings, and a private area for the calendar and management of services, users, settings, etc. There is a backend API that allows data manipulation, including listing the appointments for a specific time range. This happens on this endpoint: /index.php/backend_api/ajax_get_calendar_events Unfortunately, there is no authentication / permissions-check on that endpoint, the only required parameters in a POST request are "startDate", "endDate" and "csrfToken". Because the csrfToken can be obtained by any unauthenticated u
O3 Security · Impact-Aware SCA

Is GHSA-r6cm-wg48-rh2r in your dependencies?

O3 Security finds GHSA-r6cm-wg48-rh2r across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-r6cm-wg48-rh2r: Critical 9.1 severity | O3 Security