Unauthorized calendar modification via missing provider checks
Published Jul 17, 2023 · Updated Oct 30, 2024
Authorization bypass in Easy!Appointments before 1.5.0 allows remote authenticated users to alter other providers' calendar events. Calendar.php accepted attacker-selected provider IDs when saving or deleting appointments and unavailability records without checking provider scope. Provider or secretary access is required, and exploitation permits unauthorized calendar writes and deletions.
Summary
What happened
Authorization bypass in Easy!Appointments before 1.5.0 allows remote authenticated users to alter other providers' calendar events. Calendar.php accepted attacker-selected provider IDs when saving or deleting appointments and unavailability records without checking provider scope. Provider or secretary access is required, and exploitation permits unauthorized calendar writes and deletions.
The record
- CVE
- CVE-2023-3700
- Published
- Jul 17, 2023
- Updated
- Oct 30, 2024
- Vendor
- Alex Tselegidis
- Product
- Easy!Appointments
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 17, 2023CVE publishedPublication date reported by the CVE source.
- Oct 30, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.5.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr.dev proof-of-concept reportproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo